Triple
T12230127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | territory of Chile |
E291451
|
entity |
| Predicate | claimedInAntarcticaBetweenMeridians |
P103917
|
FINISHED |
| Object | 53°W |
—
|
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: 53°W | Statement: [territory of Chile, claimedInAntarcticaBetweenMeridians, 53°W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedInAntarcticaBetweenMeridians Context triple: [territory of Chile, claimedInAntarcticaBetweenMeridians, 53°W]
-
A.
containsAntarcticTerritory
Indicates that a geopolitical entity includes land or territory located within the Antarctic region.
-
B.
distanceFromAntarcticMainland
Indicates the measured spatial separation between a location or object and the nearest point on the Antarctic mainland.
-
C.
locatedInTheSouthernHemisphere
Indicates that the subject is situated geographically south of the Earth's equator.
-
D.
locatedAtPoleRegion
Indicates that an entity is situated within a polar region of a planetary body, such as its north or south pole area.
-
E.
firstAntarcticCircleCrossingDate
Indicates the date on which an entity first crossed the Antarctic Circle.
- F. None of above. chosen
Provenance (4 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d92468052c819090546f36d009a64f |
completed | April 10, 2026, 4:25 p.m. |
Created at: April 8, 2026, 9:51 p.m.