Triple
T23533831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obelisk of Montecitorio |
E576638
|
entity |
| Predicate | fellInAntiquity |
P153148
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Obelisk of Montecitorio, fellInAntiquity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fellInAntiquity Context triple: [Obelisk of Montecitorio, fellInAntiquity, yes]
-
A.
discoveredInAntiquity
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
-
B.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
C.
reputationInAntiquity
Indicates the reputation or standing an entity had during ancient times.
-
D.
associatedWithAncientEmpire
Indicates that one entity has a historical, cultural, political, or geographic connection or affiliation with an ancient empire.
-
E.
eraOfOriginalMonuments
Indicates the historical time period during which the original monuments were created or first established.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:10 p.m.