Triple
T6184089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phone Call from a Stranger |
E138012
|
entity |
| Predicate | disasterDepicted |
P69540
|
FINISHED |
| Object | airplane crash |
—
|
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: airplane crash | Statement: [Phone Call from a Stranger, disasterDepicted, airplane crash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disasterDepicted Context triple: [Phone Call from a Stranger, disasterDepicted, airplane crash]
-
A.
notableDisasterType
Indicates the specific kind or category of disaster for which something (such as a place, event, or entity) is notable or best known.
-
B.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
C.
supportsDisasterType
Indicates that one entity is capable of handling, responding to, or being applicable to a specified type of disaster.
-
D.
consequenceOfDestruction
Indicates that one event, state, or condition occurs as a direct result of a prior act of destruction.
-
E.
areaDestroyed
Indicates that a specified portion or region has been damaged or ruined to the point of destruction.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c061020d148190ae2edf2b363f1e24 |
completed | March 22, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:19 p.m.