Triple
T27713667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Forehead |
E698758
|
entity |
| Predicate | isSubPeakOf |
P1319
|
FINISHED |
| Object | Mount Mansfield |
—
|
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: Mount Mansfield | Statement: [The Forehead, isSubPeakOf, Mount Mansfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubPeakOf Context triple: [The Forehead, isSubPeakOf, Mount Mansfield]
-
A.
hasSubpeakRelation
Indicates that one peak is a subordinate or subsidiary summit of another, higher or primary peak.
-
B.
isMajorPeakOf
Indicates that one peak is a primary or most prominent summit within a specified mountain, range, or geographic area.
-
C.
hasSharperPeakThan
Indicates that one entity’s peak (e.g., in a graph, distribution, or signal) is more pointed or narrow than the peak of another entity.
-
D.
parentPeak
chosen
Indicates that one peak is the higher or primary peak to which another, subordinate peak is topographically related.
-
E.
isIsolatedPeak
Indicates that a peak stands distinctly apart from surrounding peaks, with significant topographic separation or prominence from nearby elevations.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 3:03 p.m.