Triple
T15204405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branscomb Glacier |
E363351
|
entity |
| Predicate | isRouteSectionOf |
P6309
|
FINISHED |
| Object | normal route on Mount Vinson |
—
|
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: normal route on Mount Vinson | Statement: [Branscomb Glacier, isRouteSectionOf, normal route on Mount Vinson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRouteSectionOf Context triple: [Branscomb Glacier, isRouteSectionOf, normal route on Mount Vinson]
-
A.
isPartOfRoute
chosen
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
B.
isNamedSectionOf
Indicates that one entity is a specifically named section or subdivision that forms part of another entity.
-
C.
isOnSectionOf
Indicates that one entity is located on, or positioned along, a specific segment or subsection of another entity.
-
D.
hasSectionIn
Indicates that one entity contains or includes another entity as a section or subdivision within it.
-
E.
appliesToSectionOf
Indicates that something is relevant or applicable specifically to a particular section or subsection of a larger whole.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b693a48190a6230b7b52bc8cd3 |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:11 a.m.