Triple
T3069544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Mountain |
E62186
|
entity |
| Predicate | summitUsedFor |
P27847
|
FINISHED |
| Object | telecommunications installations |
—
|
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: telecommunications installations | Statement: [Green Mountain, summitUsedFor, telecommunications installations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitUsedFor Context triple: [Green Mountain, summitUsedFor, telecommunications installations]
-
A.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
B.
summitAffected
Indicates that a summit, meeting, or high-level event has been influenced, impacted, or altered by a specified factor or circumstance.
-
C.
summitAccessibleFrom
Indicates that a summit can be reached or accessed starting from a specified location or route.
-
D.
summitLocatedIn
Indicates that a summit (mountain peak) is geographically situated within a specified area or region.
-
E.
hasSummitFacility
chosen
Indicates that one entity possesses or provides a facility or infrastructure located at the summit of another entity (such as a mountain, hill, or 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada100f0b8819095da366fdc6803a8 |
completed | March 8, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.