Triple
T38003712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Mountain Peak area |
E948173
|
entity |
| Predicate | nearestMajorSummit |
P126574
|
FINISHED |
| Object | White Mountain Peak |
—
|
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: White Mountain Peak | Statement: [White Mountain Peak area, nearestMajorSummit, White Mountain Peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorSummit Context triple: [White Mountain Peak area, nearestMajorSummit, White Mountain Peak]
-
A.
nearbySummit
Indicates that one summit is located close to another summit in geographic space.
-
B.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
C.
moreProminentSummit
Indicates that one summit is higher, more notable, or more significant than another in terms of prominence.
-
D.
nearestHigherPeak
chosen
Indicates that one peak is the closest peak that has a higher elevation than another specified peak.
-
E.
otherMajorPeak
Indicates that one peak is another significant or prominent peak associated with, but distinct from, a given primary peak.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.