Triple
T600451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentine Antarctica |
E11480
|
entity |
| Predicate | boundedByParallelSouth |
P13333
|
FINISHED |
| Object | 60°S |
—
|
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: 60°S | Statement: [Argentine Antarctica, boundedByParallelSouth, 60°S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundedByParallelSouth Context triple: [Argentine Antarctica, boundedByParallelSouth, 60°S]
-
A.
southernBoundaryReference
chosen
Indicates that one entity is used as the reference or defining limit for the southern boundary of another entity.
-
B.
locatedSouthOf
Indicates that one entity is positioned geographically to the south of another entity.
-
C.
locatedSouthWestOf
Indicates that one entity is positioned to the southwest of another entity, combining both a southern and western relative location.
-
D.
liesSoutheastOf
Indicates that one entity is located to the southeast of another, combining both a southern and eastern directional relationship.
-
E.
hasSouthernTerminus
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49dc4f7d08190990f70b9b3af6ce5 |
completed | March 1, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69a49cf59cd0819084e67981cb371e25 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.