Triple
T777855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julian Alps |
E16428
|
entity |
| Predicate | rangeCoordinates |
P10142
|
FINISHED |
| Object | approximate center 46.4°N 13.8°E |
—
|
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: approximate center 46.4°N 13.8°E | Statement: [Julian Alps, rangeCoordinates, approximate center 46.4°N 13.8°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeCoordinates Context triple: [Julian Alps, rangeCoordinates, approximate center 46.4°N 13.8°E]
-
A.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
B.
rangeType
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
C.
rangeCapability
Indicates the maximum distance or extent over which an entity can effectively operate, function, or exert its effect.
-
D.
coordinateRegion
Indicates that one region is geographically or spatially aligned with, or corresponds to, another region within a shared coordinate framework.
-
E.
hasCoordinates
chosen
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.