Triple
T16253212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uruguayan Air Force Flight 571 disaster |
E394563
|
entity |
| Predicate | survivalDurationDays |
P90053
|
FINISHED |
| Object | 72 |
—
|
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: 72 | Statement: [Uruguayan Air Force Flight 571 disaster, survivalDurationDays, 72]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalDurationDays Context triple: [Uruguayan Air Force Flight 571 disaster, survivalDurationDays, 72]
-
A.
averageSurvivalAfterDiagnosis
Indicates the typical length of time individuals survive following the point at which a condition or disease is first diagnosed.
-
B.
survivesFor
chosen
Indicates that one entity continues to exist, endure, or remain functional for a specified duration or period.
-
C.
survivalFunction
Indicates the probability that an entity or system continues to exist or function without failure beyond a given point in time.
-
D.
extentOfSurvivalOfWork
Indicates the degree to which a work has been preserved or remains extant.
-
E.
survivorTerm
Indicates that one entity is designated as the surviving or remaining party in relation to another entity, often after a loss, termination, or adverse event.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24598c9488190a92df7d8b1824724 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.