Triple
T36296366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Airlines Flight 11 |
E893378
|
entity |
| Predicate | intendedFlightPath |
P10707
|
FINISHED |
| Object | Boston to Los Angeles |
—
|
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: Boston to Los Angeles | Statement: [American Airlines Flight 11, intendedFlightPath, Boston to Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedFlightPath Context triple: [American Airlines Flight 11, intendedFlightPath, Boston to Los Angeles]
-
A.
intendedFlightProfile
Indicates the planned or expected way an aircraft is supposed to fly a mission, including its route, altitude, speed, and other flight parameters.
-
B.
positionFlown
Indicates the specific role or seat (e.g., pilot, co-pilot) that an individual occupied while operating or flying in an aircraft.
-
C.
flightRoute
chosen
Indicates a path or sequence of locations that a particular flight travels between, typically from its origin to its destination (and possibly via intermediate stops).
-
D.
trajectoryAssist
Indicates assistance provided in planning, adjusting, or optimizing the path or course of motion of an entity.
-
E.
trajectoryType
Indicates the kind or pattern of motion an entity follows along its path over time.
- 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_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 3, 2026, 4:09 p.m.