Triple
T13686242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sriwijaya Air |
E328134
|
entity |
| Predicate | Sriwijaya Air Flight 182 |
P83944
|
FINISHED |
| Object | crashDate 2021-01-09 |
—
|
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: crashDate 2021-01-09 | Statement: [Sriwijaya Air, Sriwijaya Air Flight 182, crashDate 2021-01-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Sriwijaya Air Flight 182 Context triple: [Sriwijaya Air, Sriwijaya Air Flight 182, crashDate 2021-01-09]
-
A.
flightNumberInAccident
chosen
Indicates that a specific flight number is associated with an accident event.
-
B.
ferryFlightIncidents
Indicates incidents or events that occurred during ferry flights, where aircraft are being repositioned rather than operating regular revenue services.
-
C.
missionAccident
Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
-
D.
aircraftInvolvedInDeath
Indicates that an aircraft played a direct role in causing or contributing to a person's death.
-
E.
aircraftLostByJapan
Indicates that the specified aircraft were lost by Japan, typically through destruction, damage beyond repair, or disappearance.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc670968881908e2b4fdf656c7285 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.