Triple
T250111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama–Florida state line near Pensacola |
E5123
|
entity |
| Predicate | hasLatitudeApprox |
P1281
|
FINISHED |
| Object | 30.6° 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: 30.6° N | Statement: [Alabama–Florida state line near Pensacola, hasLatitudeApprox, 30.6° N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatitudeApprox Context triple: [Alabama–Florida state line near Pensacola, hasLatitudeApprox, 30.6° N]
-
A.
coordinateLatitude
chosen
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
-
B.
coordinateLongitude
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
C.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
D.
hasSummitCoordinates
Indicates that an entity has specific geographic coordinates identifying the location of its summit.
-
E.
distanceFromNorthPole
Indicates the measured spatial distance between a given entity’s location and the geographic North Pole.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d3728f0819086214ccc2db2305a |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.