Triple
T31823378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falkland Plateau |
E812323
|
entity |
| Predicate | liesAtApproximateLongitude |
P1282
|
FINISHED |
| Object | 50 degrees west |
—
|
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 west | Statement: [Falkland Plateau, liesAtApproximateLongitude, 50 degrees west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesAtApproximateLongitude Context triple: [Falkland Plateau, liesAtApproximateLongitude, 50 degrees west]
-
A.
intendedLongitude
Indicates the longitude value that an entity is meant or planned to have or reach, rather than its actual current longitude.
-
B.
longitudeOfFormationApprox
Indicates an approximate longitudinal position where a formation or event originated or took shape.
-
C.
landingSiteLongitude
Indicates the longitudinal coordinate (east–west position) of a specified landing site on a planetary body.
-
D.
coordinateLongitude
chosen
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
E.
liesWithinLatitudeBand
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
- 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_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:46 p.m.