Triple
T36296352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Airlines Flight 11 |
E893378
|
entity |
| Predicate | timeOfImpact |
P33470
|
FINISHED |
| Object | 2001-09-11T08:46:00-04:00 |
—
|
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: 2001-09-11T08:46:00-04:00 | Statement: [American Airlines Flight 11, timeOfImpact, 2001-09-11T08:46:00-04:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfImpact Context triple: [American Airlines Flight 11, timeOfImpact, 2001-09-11T08:46:00-04:00]
-
A.
impactTimeLocal
chosen
Indicates the specific local time at which an impact event occurs or is expected to occur.
-
B.
fictionalTimeToImpact
Indicates the amount of time, within a fictional or hypothetical context, remaining until a specified impact event occurs.
-
C.
collisionDate
Indicates the date on which a collision event between entities occurred.
-
D.
impactPosition
Indicates the specific location or coordinates at which an impact or collision occurs between entities.
-
E.
timeOfDeath
Indicates the specific time at which an entity (typically a person or organism) died.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.