Triple
T31823377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falkland Plateau |
E812323
|
entity |
| Predicate | liesAtApproximateLatitude |
P1281
|
FINISHED |
| Object | 50 degrees south |
—
|
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: 50 degrees south | Statement: [Falkland Plateau, liesAtApproximateLatitude, 50 degrees south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesAtApproximateLatitude Context triple: [Falkland Plateau, liesAtApproximateLatitude, 50 degrees south]
-
A.
liesWithinLatitudeBand
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
B.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
-
C.
visibleAtLatitudeBetween
Indicates that something can be seen or is observable only within a specified range of latitudes.
-
D.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
E.
coordinateLatitude
chosen
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6af8130148190834cca27b2458735 |
completed | May 3, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:46 p.m.