Triple
T11854931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margerie Glacier |
E282010
|
entity |
| Predicate | hasApproximateTotalHeight |
P8271
|
FINISHED |
| Object | about 100 meters |
—
|
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: about 100 meters | Statement: [Margerie Glacier, hasApproximateTotalHeight, about 100 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateTotalHeight Context triple: [Margerie Glacier, hasApproximateTotalHeight, about 100 meters]
-
A.
totalHeight
chosen
Indicates the combined vertical measurement resulting from adding the heights of one or more entities.
-
B.
ashColumnHeightApproximate
Indicates that the height of an ash column is an estimated or approximate value rather than an exact measurement.
-
C.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
D.
hasApproximateDepth
Indicates that an entity is associated with a depth value that is not exact but estimated or approximate.
-
E.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a697f4108190af984932d2118472 |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.