Triple
T18246636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Riga |
E436967
|
entity |
| Predicate | hasCityStatusRole |
P8234
|
FINISHED |
| Object | cultural centre of Riga |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: cultural centre of Riga | Statement: [Old Riga, hasCityStatusRole, cultural centre of Riga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityStatusRole Context triple: [Old Riga, hasCityStatusRole, cultural centre of Riga]
-
A.
hasCityStatusFor
Indicates that an entity holds official city status within the jurisdiction or context of another entity.
-
B.
hasCityRole
chosen
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
C.
grantedCityStatusFor
Indicates that an authority has officially conferred city status upon an entity for a specified reason or basis.
-
D.
impliesStatusOfCity
Indicates that one entity suggests, infers, or entails a particular status or condition of a city.
-
E.
hasCityRight
Indicates that an entity possesses legal or official rights associated with a particular city, such as jurisdiction, privileges, or authority within that city.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e7d49c8190b227a13b63615754 |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.