Triple
T3845847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Zoncolan |
E93566
|
entity |
| Predicate | hasSummitFinishArea |
P8666
|
FINISHED |
| Object | near tunnel at top road section |
—
|
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 tunnel at top road section | Statement: [Monte Zoncolan, hasSummitFinishArea, near tunnel at top road section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitFinishArea Context triple: [Monte Zoncolan, hasSummitFinishArea, near tunnel at top road section]
-
A.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
B.
hasSummitMarker
Indicates that a location or peak is marked by an official summit marker or sign denoting its highest point.
-
C.
hasSummitCross
Indicates that a mountain or peak is topped by a summit cross installed at or near its highest point.
-
D.
hasSummitConditions
Indicates that specific environmental or situational conditions required for a summit (e.g., peak ascent or high-level meeting) are present or satisfied.
-
E.
hasSummitFeature
chosen
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb77a488190be7fc2a1211f1f2d |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.