Triple
T14463473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obelisk of Montecitorio |
E358643
|
entity |
| Predicate | re-erected |
P70567
|
FINISHED |
| Object | 1789 |
—
|
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: 1789 | Statement: [Obelisk of Montecitorio, re-erected, 1789]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: re-erected Context triple: [Obelisk of Montecitorio, re-erected, 1789]
-
A.
re-erectedInLocation
chosen
Indicates that something which had previously been taken down or fallen was set up again at a particular location.
-
B.
erected
Indicates that one entity caused a structure or object to be built or put upright, typically in a deliberate and often permanent manner.
-
C.
recreated
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
-
D.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
E.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
- 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.