Triple
T29094183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadly Pole to Pole |
E734942
|
entity |
| Predicate | endPointOfJourney |
P51834
|
FINISHED |
| Object | Antarctic |
—
|
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: Antarctic | Statement: [Deadly Pole to Pole, endPointOfJourney, Antarctic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endPointOfJourney Context triple: [Deadly Pole to Pole, endPointOfJourney, Antarctic]
-
A.
endLocationOfJourney
chosen
Indicates the final destination or stopping point reached at the conclusion of a journey or trip.
-
B.
railwayUpperTerminus
Indicates that a railway line or route reaches its upper (typically higher-altitude or upstream) terminal endpoint at the related location.
-
C.
transportTerminusFor
Indicates that a location serves as the endpoint or final stop for a particular transport route or service.
-
D.
direction2Terminus
Indicates the direction in which something leads toward or ends at a particular terminus or endpoint.
-
E.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6617f43748190b4880e1da320cdaa |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:07 a.m.