Triple
T14942272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E69 |
E372558
|
entity |
| Predicate | hasMaximumLatitudeApprox |
P35088
|
FINISHED |
| Object | 71.2° N |
—
|
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: 71.2° N | Statement: [European route E69, hasMaximumLatitudeApprox, 71.2° N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumLatitudeApprox Context triple: [European route E69, hasMaximumLatitudeApprox, 71.2° N]
-
A.
isSouthernmostLatitudeWhereSunCanBeOverhead
Indicates the southernmost latitude on Earth at which the Sun can appear directly overhead (at the zenith) at some time during the year.
-
B.
highestLatitudeReached
chosen
Indicates the maximum latitude that an entity has ever reached during its movement or existence.
-
C.
demandsBoundaryAtLatitude
Indicates that an entity asserts or requires that a boundary be established along a specific line of latitude.
-
D.
isBestSeenFromLatitudes
Indicates that something is most optimally or clearly observable when viewed from specific geographic latitudes.
-
E.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68c1df0819084c0cd61b207d398 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:38 a.m.