Triple
T26185871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Antarctic Ice Sheet |
E654826
|
entity |
| Predicate | hasApproximateMaximumThickness |
P55323
|
FINISHED |
| Object | over 4,000 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: over 4,000 meters | Statement: [East Antarctic Ice Sheet, hasApproximateMaximumThickness, over 4,000 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateMaximumThickness Context triple: [East Antarctic Ice Sheet, hasApproximateMaximumThickness, over 4,000 meters]
-
A.
hasMaximumThickness
chosen
Indicates that an entity possesses a specified upper limit on its thickness.
-
B.
hasThicknessRange
Indicates that an entity is associated with a minimum and maximum thickness value defining the range of its thickness.
-
C.
hasMaximumBreadth
Indicates that an entity possesses the greatest breadth (widest extent) among a set of comparable entities or within a defined context.
-
D.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
E.
hasStratigraphicThickness
Indicates the measured vertical thickness or depth extent of a stratigraphic unit or layer.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 8:42 p.m.