Triple
T13127205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cordilleran Ice Sheet |
E311874
|
entity |
| Predicate | formedLandform |
P940
|
FINISHED |
| Object | fjords of British Columbia coast |
—
|
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: fjords of British Columbia coast | Statement: [Cordilleran Ice Sheet, formedLandform, fjords of British Columbia coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedLandform Context triple: [Cordilleran Ice Sheet, formedLandform, fjords of British Columbia coast]
-
A.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
-
C.
notablePeak
Indicates that one entity is a peak or summit that is especially prominent, famous, or significant in relation to another entity.
-
D.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
-
E.
territorialPeak
Indicates the highest geographical point located within the territory or jurisdiction of a given entity.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819aac388190b59bf43cc6a49d0c |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.