Triple
T14463467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obelisk of Montecitorio |
E358643
|
entity |
| Predicate | transportedToRome |
P54321
|
FINISHED |
| Object | 10 BCE |
—
|
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: 10 BCE | Statement: [Obelisk of Montecitorio, transportedToRome, 10 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedToRome Context triple: [Obelisk of Montecitorio, transportedToRome, 10 BCE]
-
A.
transportedToRomeIn
chosen
Indicates that something or someone was transported or moved to Rome at a particular time or by a particular means.
-
B.
returnToRomeTo
Indicates that an entity goes back or returns to the location Rome.
-
C.
laterRelationToRome
Indicates that one entity occurs or exists at a time later than the reference time associated with Rome.
-
D.
initialRelationToRome
Indicates the nature of an entity’s earliest recorded or original relationship, status, or connection to Rome.
-
E.
wasTransportedTo
Indicates that an entity was moved or carried from one location to another, resulting in its arrival at the specified destination.
- 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.