Triple
T16431332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic Ice Sheet |
E399075
|
entity |
| Predicate | containsRecord |
P122753
|
FINISHED |
| Object | long climate history in ice cores |
—
|
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: long climate history in ice cores | Statement: [Antarctic Ice Sheet, containsRecord, long climate history in ice cores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRecord Context triple: [Antarctic Ice Sheet, containsRecord, long climate history in ice cores]
-
A.
isRecord
Indicates that one entity functions as an official or authoritative record of another entity or of some information.
-
B.
currentContains
Indicates that one entity presently includes, encloses, or has another entity within its bounds or scope.
-
C.
hasRecordType
Indicates that an entity is associated with or classified under a specific type or category of record.
-
D.
hasEntryOn
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
E.
containsCard
Indicates that one entity includes or holds a specific card as part of its contents or collection.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.