Triple
T27546746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ara Zobayan |
E695382
|
entity |
| Predicate | knownPassengerOnAccidentFlight |
P881
|
FINISHED |
| Object | Kobe Bryant |
—
|
NE NERFINISHED |
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: Kobe Bryant | Statement: [Ara Zobayan, knownPassengerOnAccidentFlight, Kobe Bryant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownPassengerOnAccidentFlight Context triple: [Ara Zobayan, knownPassengerOnAccidentFlight, Kobe Bryant]
-
A.
coPassengerInFatalCrashWith
Indicates that two or more individuals were passengers in the same vehicle involved in a fatal crash.
-
B.
passengers
chosen
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
C.
flightNumberInAccident
Indicates that a specific flight number is associated with an accident event.
-
D.
fatalitiesOnboard
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
-
E.
survivorsInFinalAccident
Indicates that the referenced entities are those who remained alive after the final accident in a sequence of accidents.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 1:33 p.m.