Triple
T24714908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yelcho |
E612132
|
entity |
| Predicate | rescueLeaderOnBoard |
P157686
|
FINISHED |
| Object | Ernest Shackleton |
—
|
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: Ernest Shackleton | Statement: [Yelcho, rescueLeaderOnBoard, Ernest Shackleton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescueLeaderOnBoard Context triple: [Yelcho, rescueLeaderOnBoard, Ernest Shackleton]
-
A.
targetLeader
Indicates that one entity is the primary leader, focal authority, or main decision-maker targeted or referenced by another entity or action.
-
B.
designatedLeader
Indicates that one entity has been formally chosen or assigned to serve as the leader of another entity or group.
-
C.
establishedUnderLeader
Indicates that an entity was founded, created, or formally established during the tenure or authority of a specific leader.
-
D.
linkedToLeader
Indicates that an entity has a direct connection, association, or relationship with a leader.
-
E.
capturedLeader
Indicates that one party has taken control of and detained the primary leader of another group or entity.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 3:33 a.m.