Triple
T33357085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endurance (ship) |
E854101
|
entity |
| Predicate | expeditionGoal |
P24308
|
FINISHED |
| Object | crossing of the Antarctic continent |
—
|
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: crossing of the Antarctic continent | Statement: [Endurance (ship), expeditionGoal, crossing of the Antarctic continent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expeditionGoal Context triple: [Endurance (ship), expeditionGoal, crossing of the Antarctic continent]
-
A.
expeditionObjective
chosen
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
B.
issExpedition
Indicates an expedition or mission associated with the International Space Station (ISS).
-
C.
expeditionEvent
Indicates an event or occurrence that takes place as part of, or in direct connection with, an expedition.
-
D.
organizedExpedition
Indicates that an entity planned, coordinated, and arranged the details of an expedition or journey.
-
E.
describesExpedition
Indicates that one entity provides a detailed account or characterization of an expedition undertaken by another entity.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.