Triple
T9128398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cryptozoic |
E219021
|
entity |
| Predicate | approximateEndAge |
P52881
|
FINISHED |
| Object | about 541 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: about 541 million years ago | Statement: [Cryptozoic, approximateEndAge, about 541 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateEndAge Context triple: [Cryptozoic, approximateEndAge, about 541 million years ago]
-
A.
approximateAgeMa
Indicates that one entity has an estimated or approximate age value relative to another reference (such as a person or event).
-
B.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
C.
approximateAgeBeforePresent
chosen
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
D.
typicallyIssuedAtAge
Indicates the age at which something is most commonly or customarily issued to an individual.
-
E.
endYearApprox
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8cc85b081908ee80db0e3b7df15 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.