Triple
T14463469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obelisk of Montecitorio |
E358643
|
entity |
| Predicate | originalFunctionInRome |
P4098
|
FINISHED |
| Object | gnomon of a giant solar meridian |
—
|
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: gnomon of a giant solar meridian | Statement: [Obelisk of Montecitorio, originalFunctionInRome, gnomon of a giant solar meridian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalFunctionInRome Context triple: [Obelisk of Montecitorio, originalFunctionInRome, gnomon of a giant solar meridian]
-
A.
originalFunction
chosen
Indicates that one entity serves as the initial or primary function from which another function or behavior is derived or defined.
-
B.
originalRomanLocation
Indicates the original geographic location of a place or entity during the period of ancient Roman rule or in the context of the Roman world.
-
C.
returnToRomeTo
Indicates that an entity goes back or returns to the location Rome.
-
D.
initialRelationToRome
Indicates the nature of an entity’s earliest recorded or original relationship, status, or connection to Rome.
-
E.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91ad67bc81908ecdaa7262f6dc55 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.