Triple
T25391407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaalbara supercraton |
E636175
|
entity |
| Predicate | hasMaximumAge |
P155815
|
FINISHED |
| Object | about 2.7 billion 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: about 2.7 billion years | Statement: [Vaalbara supercraton, hasMaximumAge, about 2.7 billion years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumAge Context triple: [Vaalbara supercraton, hasMaximumAge, about 2.7 billion years]
-
A.
hasMaximumAgeInGa
chosen
Indicates that an entity has an upper age limit, measured in billions of years (giga-annum, Ga).
-
B.
hasRemainingLifespan
Indicates that an entity still has a certain amount of time or capacity left before it reaches the end of its expected lifespan or usability.
-
C.
maximumAgeInYears
Indicates the highest allowable or observed age, expressed in years, associated with an entity or condition.
-
D.
maximumAgeMa
Indicates that there is a specified maximum age limit applicable to an entity or relationship.
-
E.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 21, 2026, 1:49 p.m.