Triple
T25276533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zambia national football team |
E633709
|
entity |
| Predicate | 1993AirDisasterLocation |
P64753
|
FINISHED |
| Object | off the coast of Gabon |
—
|
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: off the coast of Gabon | Statement: [Zambia national football team, 1993AirDisasterLocation, off the coast of Gabon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1993AirDisasterLocation Context triple: [Zambia national football team, 1993AirDisasterLocation, off the coast of Gabon]
-
A.
aircraftAccident
Indicates that an event involves an aircraft experiencing an accident, such as a crash, collision, or serious malfunction during operation.
-
B.
planeCrashLocation
chosen
Indicates the location where a plane crash occurred.
-
C.
missionAccident
Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
-
D.
flightNumberInAccident
Indicates that a specific flight number is associated with an accident event.
-
E.
causeOf1993Fire
Indicates the entity that was responsible for starting or bringing about the 1993 fire.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba6eb208190823b251f5888044a |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:17 p.m.