Triple
T3020307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jengish Chokusu |
E82437
|
entity |
| Predicate | rangeCoordinatesApprox |
P10760
|
FINISHED |
| Object | 42.0°N 80.1°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: 42.0°N 80.1°E | Statement: [Jengish Chokusu, rangeCoordinatesApprox, 42.0°N 80.1°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeCoordinatesApprox Context triple: [Jengish Chokusu, rangeCoordinatesApprox, 42.0°N 80.1°E]
-
A.
hasApproximateCoordinates
chosen
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
B.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
C.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
-
D.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
E.
hasApproximateExtent
Indicates that one entity has a spatial, temporal, or quantitative extent that is only roughly or approximately specified rather than exact.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a940c048190bc46e2c8001db8c0 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.