Triple
T24714906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yelcho |
E612132
|
entity |
| Predicate | rescuedCrewOf |
P7320
|
FINISHED |
| Object | Endurance (ship) |
—
|
NE NERFINISHED |
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: Endurance (ship) | Statement: [Yelcho, rescuedCrewOf, Endurance (ship)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescuedCrewOf Context triple: [Yelcho, rescuedCrewOf, Endurance (ship)]
-
A.
crewRescued
Indicates that a crew has been successfully saved from danger or a threatening situation.
-
B.
rescuedBy
chosen
Indicates that one entity has been saved or brought out of danger by another entity.
-
C.
rescuedDuring
Indicates that one entity was rescued in the course of, or as part of, a specified event or time period.
-
D.
rescuedTo
Indicates that one entity has been saved or freed from danger, harm, or a problematic situation and brought to the safety or custody of another entity or location.
-
E.
crewSurvivorsOnReturn
Indicates that the members of a crew remained alive and successfully returned from a mission or journey.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:33 a.m.