Triple
T35705965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost |
E1031717
|
entity |
| Predicate | flightNumberInStory |
P184077
|
FINISHED |
| Object | 815 |
—
|
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: 815 | Statement: [Lost, flightNumberInStory, 815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightNumberInStory Context triple: [Lost, flightNumberInStory, 815]
-
A.
flightNumberInProgram
Indicates that a specific flight is associated with, or belongs to, a particular program or schedule under a given flight number.
-
B.
flightNumberAtTimeOfEvent
Indicates the specific flight number associated with an entity at the time a particular event occurred.
-
C.
flightNumberInAccident
Indicates that a specific flight number is associated with an accident event.
-
D.
wingNumber
Indicates the specific identifier or count assigned to a wing associated with an entity.
-
E.
flightRecord
Indicates a record of a specific flight event or journey, capturing details about its occurrence and characteristics.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.