Triple
T38206091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Peak of Goose Eye Mountain |
E1009203
|
entity |
| Predicate | isNearbyFeatureOf |
P2064
|
FINISHED |
| Object | Appalachian Trail corridor in the Mahoosucs |
—
|
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: Appalachian Trail corridor in the Mahoosucs | Statement: [East Peak of Goose Eye Mountain, isNearbyFeatureOf, Appalachian Trail corridor in the Mahoosucs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearbyFeatureOf Context triple: [East Peak of Goose Eye Mountain, isNearbyFeatureOf, Appalachian Trail corridor in the Mahoosucs]
-
A.
nearbyFeature
chosen
Indicates that one entity is located close to or in the immediate vicinity of another entity.
-
B.
hasNearbyTrailFeature
Indicates that one entity has another entity as a trail-related feature located in close physical proximity.
-
C.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
D.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
E.
hasNearbyPoint
Indicates that one entity has at least one other point located within a specified proximity or distance from it.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.