Triple
T28917347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reid Headwall |
E733405
|
entity |
| Predicate | proximityToSummit |
P44470
|
FINISHED |
| Object | near upper slopes of Mount Hood |
—
|
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: near upper slopes of Mount Hood | Statement: [Reid Headwall, proximityToSummit, near upper slopes of Mount Hood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityToSummit Context triple: [Reid Headwall, proximityToSummit, near upper slopes of Mount Hood]
-
A.
distanceToSummit
Indicates the measured or estimated distance remaining from a given point to the summit of a feature or elevation.
-
B.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
C.
positionRelativeToSummit
chosen
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
D.
nearbySummit
Indicates that one summit is located close to another summit in geographic space.
-
E.
stoppedDistanceBelowSummit
Indicates that an entity came to a stop at a location that is a certain distance short of reaching the summit.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b160fa48190958da6070e8385fe |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:16 a.m.