Triple
T1304166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yelcho |
E27835
|
entity |
| Predicate | rescuedGroup |
P7320
|
FINISHED |
| Object | Endurance expedition members |
—
|
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: Endurance expedition members | Statement: [Yelcho, rescuedGroup, Endurance expedition members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescuedGroup Context triple: [Yelcho, rescuedGroup, Endurance expedition members]
-
A.
rescuedBy
chosen
Indicates that one entity has been saved or brought out of danger by another entity.
-
B.
transportedGroup
Indicates that one entity moved or carried a group of entities from one location to another.
-
C.
estimatedNumberOfPeopleSaved
Indicates the approximate count of individuals whose lives were preserved or harm was averted as a result of a particular action, intervention, or entity.
-
D.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
E.
helpedEscape
Indicates that one entity assisted another in getting away from confinement, danger, or pursuit.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c13393388190b784d6bd8c447dda |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.