Triple
T9024034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostankino Tower |
E215998
|
entity |
| Predicate | experiencedFire |
P27153
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Ostankino Tower, experiencedFire, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedFire Context triple: [Ostankino Tower, experiencedFire, 1998]
-
A.
fires
Indicates that an agent initiates the discharge or ignition of something, such as a weapon, engine, or explosive device, causing it to operate or go off.
-
B.
notableFire
chosen
Indicates that a significant or historically important fire event is associated with the subject.
-
C.
underFire
Indicates that an entity is being attacked, heavily criticized, or subjected to intense pressure by another entity or group.
-
D.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
E.
experiencedFailure
Indicates that an entity has undergone or encountered a failure in performing an action, achieving a goal, or maintaining a desired state.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7a770081908dfe3ce3374a04ba |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.