Triple
T2110080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Airlines Flight 175 |
E42480
|
entity |
| Predicate | sequenceIn911Attacks |
P4074
|
FINISHED |
| Object | second plane to strike the World Trade Center |
—
|
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: second plane to strike the World Trade Center | Statement: [United Airlines Flight 175, sequenceIn911Attacks, second plane to strike the World Trade Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceIn911Attacks Context triple: [United Airlines Flight 175, sequenceIn911Attacks, second plane to strike the World Trade Center]
-
A.
numberOfVictimsFrom2001Attacks
Indicates the count of victims resulting from the 2001 attacks associated with a given entity.
-
B.
numberOfHijackers
Indicates the quantity of individuals who carried out or attempted to carry out a hijacking in the described event or context.
-
C.
sequenceInBeagleVoyages
Indicates that one event, observation, or item occurs at a specific position within the ordered sequence of Beagle voyages.
-
D.
bombingLocation
Indicates the place where a bombing event occurs or is carried out.
-
E.
partOfSeriesOfEvents
chosen
Indicates that an event is one element within a larger, ordered sequence of related events.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae1bacc8190beffc9d0470e9190 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.