Triple
T29793509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian Orthodox Cathedral of St. Demetrius |
E756476
|
entity |
| Predicate | isLocatedInOldTown |
P110746
|
FINISHED |
| Object | Sremska Mitrovica city center |
—
|
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: Sremska Mitrovica city center | Statement: [Serbian Orthodox Cathedral of St. Demetrius, isLocatedInOldTown, Sremska Mitrovica city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInOldTown Context triple: [Serbian Orthodox Cathedral of St. Demetrius, isLocatedInOldTown, Sremska Mitrovica city center]
-
A.
isInOldTownArea
chosen
Indicates that an entity is located within the designated old town area of a place.
-
B.
isInOldTownNetwork
Indicates that an entity is part of, or connected to, a designated "Old Town" network or system.
-
C.
isLocatedDowntown
Indicates that an entity is situated within the downtown area of a city or town.
-
D.
locatedInOldCity
Indicates that an entity is situated within the boundaries of an old or historic part of a city.
-
E.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 29, 2026, 5:13 p.m.