Triple
T35700644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dartmouth Skiway |
E1031571
|
entity |
| Predicate | homeMountainOf |
P183835
|
FINISHED |
| Object | Dartmouth College alpine ski teams |
—
|
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: Dartmouth College alpine ski teams | Statement: [Dartmouth Skiway, homeMountainOf, Dartmouth College alpine ski teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeMountainOf Context triple: [Dartmouth Skiway, homeMountainOf, Dartmouth College alpine ski teams]
-
A.
parentMountain
Indicates that one mountain is considered the larger or primary "parent" from which another, related "child" mountain is derived or associated.
-
B.
mountainAccess
Indicates that an entity has the ability, right, or means to reach, enter, or utilize a mountain or mountainous area.
-
C.
borderMountainOf
Indicates that a mountain lies along or forms part of the border of a specified region or entity.
-
D.
endPointMountain
Indicates that a path, route, or boundary terminates at a mountain.
-
E.
otherHolyMountains
Indicates that an entity is associated with additional sacred or holy mountains beyond a primary one already referenced.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.