Triple
T30759727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkner Island |
E783196
|
entity |
| Predicate | almostEntirelyBuriedUnder |
P35790
|
FINISHED |
| Object | Antarctic ice sheet |
—
|
NE NERFINISHED |
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: Antarctic ice sheet | Statement: [Berkner Island, almostEntirelyBuriedUnder, Antarctic ice sheet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: almostEntirelyBuriedUnder Context triple: [Berkner Island, almostEntirelyBuriedUnder, Antarctic ice sheet]
-
A.
buriedUnder
chosen
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
B.
buriedAs
Indicates that one entity is interred or laid to rest in the manner, role, or context specified by another entity.
-
C.
buriedDepth
Indicates the depth at which one entity is buried beneath a reference surface or another entity.
-
D.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
-
E.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f9a8f888190b7b14dc5b0bc86ca |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.