Triple
T19548494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lac Manicouagan |
E489135
|
entity |
| Predicate | impactAgeEstimate |
P16042
|
FINISHED |
| Object | approximately 214 ± 1 million years |
—
|
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 214 ± 1 million years | Statement: [Lac Manicouagan, impactAgeEstimate, approximately 214 ± 1 million years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactAgeEstimate Context triple: [Lac Manicouagan, impactAgeEstimate, approximately 214 ± 1 million years]
-
A.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
B.
ageProgression
Indicates a temporal relationship where an entity’s age increases or advances over time.
-
C.
estimatedAgeInMillionsOfYears
chosen
Indicates the approximate age of something expressed in units of millions of years.
-
D.
impactBuilding
Indicates that one entity physically collides with or strikes a building, causing an impact event.
-
E.
ageModel
Indicates a relationship where one entity specifies or provides the age of another entity, typically in terms of a particular age value or age-related classification.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d2e5e588190ac3a6f612d4fb54b |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.