Triple
T9815041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis Philippe Plateau |
E238380
|
entity |
| Predicate | polarRegion |
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: [Louis Philippe Plateau, polarRegion, Antarctic region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polarRegion Context triple: [Louis Philippe Plateau, polarRegion, Antarctic region]
-
A.
polarRegions
chosen
Indicates that something is located in, associated with, or characteristic of the Earth's polar regions (the Arctic or Antarctic).
-
B.
locatedAtPoleRegion
Indicates that an entity is situated within a polar region of a planetary body, such as its north or south pole area.
-
C.
locatedInSubarcticRegion
Indicates that something exists or occurs within a subarctic geographic region characterized by cold climates just south of the Arctic.
-
D.
hasPolynya
Indicates that one entity (typically a geographic region or body of water) contains or is associated with a polynya, i.e., an area of open water surrounded by sea ice.
-
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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f19660819083e3f15780352052 |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:30 p.m.