Triple
T7829255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | January 26, 2020 Calabasas helicopter crash |
E181323
|
entity |
| Predicate | flightPurpose |
P79244
|
FINISHED |
| Object | travel to youth basketball tournament |
—
|
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: travel to youth basketball tournament | Statement: [January 26, 2020 Calabasas helicopter crash, flightPurpose, travel to youth basketball tournament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightPurpose Context triple: [January 26, 2020 Calabasas helicopter crash, flightPurpose, travel to youth basketball tournament]
-
A.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
-
B.
flightStyle
Indicates the characteristic manner or pattern in which an entity performs or exhibits flight.
-
C.
airlinesUse
Indicates that certain airlines operate, employ, or make use of a specified resource, service, or system.
-
D.
flightOverWater
Indicates that a flight’s route passes over a body of water.
-
E.
fliesWith
Indicates that one entity travels through the air in the company of, or using the same aircraft or flying means as, another entity.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04aaed1881908e1da129a43ef9c7 |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:44 p.m.