Triple
T31886053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AL 288-1 |
E814010
|
entity |
| Predicate | estimatedAgeRangeInMillionsOfYears |
P16042
|
FINISHED |
| Object | 3.18–3.22 |
—
|
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: 3.18–3.22 | Statement: [AL 288-1, estimatedAgeRangeInMillionsOfYears, 3.18–3.22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedAgeRangeInMillionsOfYears Context triple: [AL 288-1, estimatedAgeRangeInMillionsOfYears, 3.18–3.22]
-
A.
estimatedAgeInMillionsOfYears
chosen
Indicates the approximate age of something expressed in units of millions of years.
-
B.
geologicalAge
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
-
C.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
D.
age_billionYears
Indicates the number of billions of years that have elapsed since the referenced entity originated or came into existence.
-
E.
estimatedAgeYears
Indicates the approximate number of years assigned as an entity’s age based on estimation rather than exact measurement.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 30, 2026, 11:57 p.m.