Triple
T9506727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pannotia |
E229288
|
entity |
| Predicate | endExistence |
P17487
|
FINISHED |
| Object | approximately 540 million years ago |
—
|
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: approximately 540 million years ago | Statement: [Pannotia, endExistence, approximately 540 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endExistence Context triple: [Pannotia, endExistence, approximately 540 million years ago]
-
A.
concludesExistenceOf
Indicates that one entity determines or infers that another entity exists.
-
B.
hasNoLongerExistsAs
Indicates that an entity previously existed in a certain form, state, or identity but no longer exists in that form.
-
C.
existedUntil
chosen
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
-
D.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
E.
existsIf
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98543b1881908b537abdc1d2f9c0 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.