Triple
T21949305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mackay Glacier (Laurie Island) |
E542019
|
entity |
| Predicate | locatedInPolarRegion |
P14601
|
FINISHED |
| Object | Antarctic region |
—
|
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: Antarctic region | Statement: [Mackay Glacier (Laurie Island), locatedInPolarRegion, Antarctic region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPolarRegion Context triple: [Mackay Glacier (Laurie Island), locatedInPolarRegion, Antarctic region]
-
A.
locatedAtPoleRegion
Indicates that an entity is situated within a polar region of a planetary body, such as its north or south pole area.
-
B.
polarRegions
chosen
Indicates that something is located in, associated with, or characteristic of the Earth's polar regions (the Arctic or Antarctic).
-
C.
locatedInSubarcticRegion
Indicates that something exists or occurs within a subarctic geographic region characterized by cold climates just south of the Arctic.
-
D.
isInAntarcticRegion
Indicates that something is located within the geographic area defined as the Antarctic region.
-
E.
containsAntarcticTerritory
Indicates that a geopolitical entity includes land or territory located within the Antarctic region.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243aed048190b4342899c83b38ec |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:58 p.m.