Triple
T206497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctica |
E4620
|
entity |
| Predicate | coveredBy |
P6130
|
FINISHED |
| Object | Antarctic ice sheet |
—
|
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 ice sheet | Statement: [Antarctica, coveredBy, Antarctic ice sheet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredBy Context triple: [Antarctica, coveredBy, Antarctic ice sheet]
-
A.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
B.
originallyCoveredBy
Indicates that something was first protected, reported on, or documented by a particular source, medium, or entity before any others.
-
C.
overlies
chosen
Indicates that one entity is positioned directly above and covering or resting on another entity, often with partial or complete contact.
-
D.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
E.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.