Triple
T27546738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ara Zobayan |
E695382
|
entity |
| Predicate | operatorOfAccidentFlight |
P195763
|
FINISHED |
| Object | Island Express Helicopters |
—
|
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: Island Express Helicopters | Statement: [Ara Zobayan, operatorOfAccidentFlight, Island Express Helicopters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorOfAccidentFlight Context triple: [Ara Zobayan, operatorOfAccidentFlight, Island Express Helicopters]
-
A.
operatorOfAccidentAircraft
chosen
Indicates that an entity is the organization or individual responsible for operating the aircraft involved in an accident.
-
B.
aircraftAccident
Indicates that an event involves an aircraft experiencing an accident, such as a crash, collision, or serious malfunction during operation.
-
C.
accidentInvolvedAircraft
Indicates that an aircraft was directly involved in an accident or incident.
-
D.
missionAccident
Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
-
E.
accidentAirport
Indicates the airport at which an accident involving the subject entity occurred.
- 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_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 27, 2026, 1:33 p.m.