Triple
T32965727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huronian Supergroup |
E843361
|
entity |
| Predicate | ageStart |
P87250
|
FINISHED |
| Object | about 2.5 billion 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 2.5 billion years ago | Statement: [Huronian Supergroup, ageStart, about 2.5 billion years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageStart Context triple: [Huronian Supergroup, ageStart, about 2.5 billion years ago]
-
A.
approximateStartAge
chosen
Indicates the estimated or roughly determined age at which an event, condition, or state begins.
-
B.
typicallyIssuedAtAge
Indicates the age at which something is most commonly or customarily issued to an individual.
-
C.
ageAtStartOfRole
Indicates the age an entity was when they first began a specified role or position.
-
D.
ageType
Indicates the specific categorization or classification of an age value (e.g., actual, estimated, range-based) associated with an entity.
-
E.
startedTrainingAtAge
Indicates the age at which an entity first began a particular training or practice.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1a24e888190921a70d77cf06a05 |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.