Triple
T30034732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stara Varoš |
E763121
|
entity |
| Predicate | roleInCityIdentity |
P8234
|
FINISHED |
| Object | symbol of old Podgorica |
—
|
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: symbol of old Podgorica | Statement: [Stara Varoš, roleInCityIdentity, symbol of old Podgorica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCityIdentity Context triple: [Stara Varoš, roleInCityIdentity, symbol of old Podgorica]
-
A.
notableCityIdentity
Indicates that an entity is recognized or distinguished specifically in the context or identity of a particular city.
-
B.
hasCityRole
chosen
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
C.
homeCityRole
Indicates that an entity holds or held a specific role, position, or function associated with their home city.
-
D.
roleInDarkCity
Indicates that an entity has a specific role, function, or character within the context of the work "Dark City."
-
E.
focusCityRole
Indicates that a city serves a particular primary role or function within a broader geographic or organizational context.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
Created at: April 29, 2026, 6:50 p.m.