Triple
T16431287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic Ice Sheet |
E399075
|
entity |
| Predicate | restsOn |
P13359
|
FINISHED |
| Object | Antarctic bedrock |
—
|
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: Antarctic bedrock | Statement: [Antarctic Ice Sheet, restsOn, Antarctic bedrock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restsOn Context triple: [Antarctic Ice Sheet, restsOn, Antarctic bedrock]
-
A.
sitsAtop
chosen
Indicates that one entity is positioned directly on top of another, typically resting upon its upper surface.
-
B.
endsOn
Indicates that one entity terminates or concludes precisely at the boundary or endpoint of another entity.
-
C.
sitsAbove
Indicates that one entity is positioned directly higher than and vertically over another entity.
-
D.
hasStandsOn
Indicates that one entity is physically supported by and in contact with the upper surface of another entity.
-
E.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32b9dffe48190a23852f828af55d8 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.