Triple
T29393268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branscomb Glacier route |
E745426
|
entity |
| Predicate | continentHighPointRouteFor |
P180793
|
FINISHED |
| Object | Antarctica |
—
|
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: Antarctica | Statement: [Branscomb Glacier route, continentHighPointRouteFor, Antarctica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentHighPointRouteFor Context triple: [Branscomb Glacier route, continentHighPointRouteFor, Antarctica]
-
A.
stateHighPointRouteFor
Indicates that a route or path leads to or passes through the highest geographical point within a given state.
-
B.
countryHighestPointAccess
Indicates that an entity has access to, or the ability to reach or utilize, the highest geographical point within a specified country.
-
C.
trailHighPointOf
Indicates that one location is the highest elevation point along a specified trail or route.
-
D.
highestRoadPassIn
Indicates that a location contains the highest-elevation road pass within a specified area or region.
-
E.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 28, 2026, 2:44 p.m.