Triple
T1346050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amundsen Sea |
E28572
|
entity |
| Predicate | continentalShelf |
P14279
|
FINISHED |
| Object | wide and relatively deep shelf |
—
|
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: wide and relatively deep shelf | Statement: [Amundsen Sea, continentalShelf, wide and relatively deep shelf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentalShelf Context triple: [Amundsen Sea, continentalShelf, wide and relatively deep shelf]
-
A.
continentalShelfRegion
chosen
Indicates that a region lies on or corresponds to the submerged continental shelf adjacent to a continent.
-
B.
continentalPortion
Indicates that one entity represents the part or portion of a continent to which the other entity belongs or is associated.
-
C.
continent
Indicates that one entity is a continent on which the other entity is geographically located or to which it belongs.
-
D.
oceanicPortion
Indicates that one entity is a part or segment of an ocean or oceanic area in relation to another entity.
-
E.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23e84188190b0395c57dd45b62a |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.