Triple
T17156677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obelisk of Domitian |
E416359
|
entity |
| Predicate | wasToppled |
P126332
|
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 Domitian, wasToppled, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasToppled Context triple: [Obelisk of Domitian, wasToppled, yes]
-
A.
overthrownIn
Indicates that one entity (such as a government, leader, or regime) was removed from power or defeated in a specific event, context, or time period represented by the other entity.
-
B.
overthrownWithHelpOf
Indicates that one entity was removed from power or defeated through the assistance, support, or intervention of another specified entity.
-
C.
houseOverthrown
Indicates that a ruling house or dynasty has been forcibly removed from power or authority.
-
D.
overthrewGovernment
Indicates that an entity forcibly removed an existing government from power, typically replacing it with a new regime.
-
E.
wasDeposedAt
Indicates that an entity lost its position, power, or office through deposition at a specific time or event.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f40bf9ec8190b16372bcd091db9b |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:37 a.m.