Triple
T26185875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Antarctic Ice Sheet |
E654826
|
entity |
| Predicate | beganForming |
P19545
|
FINISHED |
| Object | Eocene–Oligocene transition |
—
|
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: Eocene–Oligocene transition | Statement: [East Antarctic Ice Sheet, beganForming, Eocene–Oligocene transition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganForming Context triple: [East Antarctic Ice Sheet, beganForming, Eocene–Oligocene transition]
-
A.
began
chosen
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
B.
areFormedAt
Indicates that entities come into existence, are created, or take shape at a specific location, time, or context.
-
C.
mainFormationPeriod
Indicates the time span during which something was primarily formed or took shape.
-
D.
hasFormationStage
Indicates that an entity is associated with a particular stage or phase in its formation or development process.
-
E.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
- 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_69f60c9df1ac8190a31d3a3fea0b2e16 |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:42 p.m.