Triple
T23533834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obelisk of Montecitorio |
E576638
|
entity |
| Predicate | reerectedIn |
P126333
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Obelisk of Montecitorio, reerectedIn, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reerectedIn Context triple: [Obelisk of Montecitorio, reerectedIn, 18th century]
-
A.
re-erectedInLocation
Indicates that something which had previously been taken down or fallen was set up again at a particular location.
-
B.
reErectedAt
Indicates that something was rebuilt or re-erected at a particular location or site.
-
C.
rebuiltOnSiteOf
Indicates that a structure was reconstructed or newly built on the same physical location where an earlier structure once stood.
-
D.
reconstructedBuilding
Indicates that a building has been rebuilt or restored after damage, destruction, or significant alteration.
-
E.
reerectionDate
chosen
Indicates the date on which something that was previously removed, dismantled, or taken down is erected or put back up again.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae14ae3c8190aa2714ea07a4658a |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.