Triple
T8597215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glisan Glacier |
E203580
|
entity |
| Predicate | hasPrimaryComposition |
P82021
|
FINISHED |
| Object | ice |
—
|
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: ice | Statement: [Glisan Glacier, hasPrimaryComposition, ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryComposition Context triple: [Glisan Glacier, hasPrimaryComposition, ice]
-
A.
hasPrimaryConstituent
chosen
Indicates that one entity serves as the main or principal component, ingredient, or element of another entity.
-
B.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
C.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
D.
hasPrimaryCode
Indicates that an entity is associated with its main or most important identifying code among potentially multiple codes.
-
E.
hasMajorComponent
Indicates that one entity includes another entity as a primary or most significant component or part.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46cacbe88190b95beeedc9f480b0 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:24 p.m.