Triple
T38111621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Steere |
E951668
|
entity |
| Predicate | continentSector |
P17379
|
FINISHED |
| Object | West Antarctica |
—
|
NE NERFINISHED |
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: West Antarctica | Statement: [Mount Steere, continentSector, West Antarctica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentSector Context triple: [Mount Steere, continentSector, West Antarctica]
-
A.
continentB
Indicates that the subject entity is a continent that contains or is associated with the object entity (such as a country, region, or location).
-
B.
continent
Indicates that one entity is a continent on which the other entity is geographically located or to which it belongs.
-
C.
continentalPortion
chosen
Indicates that one entity represents the part or portion of a continent to which the other entity belongs or is associated.
-
D.
continentScope
Indicates that something applies within, is limited to, or is defined at the level of a specific continent.
-
E.
continentInvolved
Indicates that a particular continent participates in, is affected by, or plays a role in a specified event, process, or relationship.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 3, 2026, 4:21 p.m.