Triple
T36227682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ana Lucia Cortez |
E891148
|
entity |
| Predicate | crashSurvivorOf |
P96743
|
FINISHED |
| Object | Oceanic Flight 815 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: Oceanic Flight 815 crash | Statement: [Ana Lucia Cortez, crashSurvivorOf, Oceanic Flight 815 crash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crashSurvivorOf Context triple: [Ana Lucia Cortez, crashSurvivorOf, Oceanic Flight 815 crash]
-
A.
isSurvivorOf
chosen
Indicates that one entity has lived through, endured, or remained alive after a particular event, condition, or harmful circumstance involving another entity.
-
B.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
-
C.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
D.
survivedAccident
Indicates that an entity continued to live or remain unharmed after being involved in an accident.
-
E.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5a0d2a48190a32496970ed5f223 |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.