Triple
T26837612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal Cluster |
E675679
|
entity |
| Predicate | distanceToMountainCluster |
P198181
|
FINISHED |
| Object | approximately 40 km |
—
|
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: approximately 40 km | Statement: [Coastal Cluster, distanceToMountainCluster, approximately 40 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMountainCluster Context triple: [Coastal Cluster, distanceToMountainCluster, approximately 40 km]
-
A.
mountainClusterLocation
Indicates the spatial relationship specifying where a particular cluster or group of mountains is located.
-
B.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
-
C.
mountainClusterCity
Indicates a relationship where a city is located within or closely associated with a specific cluster of mountains.
-
D.
distanceToAlps
Indicates the spatial distance between a given location or entity and the Alps.
-
E.
distanceToSummit
Indicates the measured or estimated distance remaining from a given point to the summit of a feature or elevation.
- F. None of above. chosen
Provenance (4 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
| PDg | Predicate description generation | batch_69fed098328c819085979de6b179b378 |
completed | May 9, 2026, 6:13 a.m. |
Created at: April 27, 2026, 5:05 a.m.