Triple
T11281461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vatnajökull ice cap |
E267074
|
entity |
| Predicate | hasAverageThickness |
P1176
|
FINISHED |
| Object | approximately 400 to 500 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: approximately 400 to 500 meters | Statement: [Vatnajökull ice cap, hasAverageThickness, approximately 400 to 500 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAverageThickness Context triple: [Vatnajökull ice cap, hasAverageThickness, approximately 400 to 500 meters]
-
A.
hasMaximumThickness
Indicates that an entity possesses a specified upper limit on its thickness.
-
B.
thickness
Indicates the measure of how deep or wide an object or layer is from one surface or side to its opposite.
-
C.
hasAverageDepth
chosen
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
D.
typicalThicknessFormula
Indicates the standard or commonly used formula for calculating the thickness of something under typical conditions.
-
E.
isThickenedWith
Indicates that one substance has been made more viscous or dense by adding another substance that serves as a thickening agent.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e96e15708190b3a1cccfbbe65882 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.