Triple
T26013357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liquid Rainbow |
E646958
|
entity |
| Predicate | ageOfBedrock |
P16042
|
FINISHED |
| Object | over 1 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: over 1 billion years | Statement: [Liquid Rainbow, ageOfBedrock, over 1 billion years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageOfBedrock Context triple: [Liquid Rainbow, ageOfBedrock, over 1 billion years]
-
A.
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.
-
B.
estimatedAgeInMillionsOfYears
chosen
Indicates the approximate age of something expressed in units of millions of years.
-
C.
hasApproximateDipOfOlderRocks
Indicates that the dip (inclination) of older rock layers is approximately equal to a specified dip value or orientation.
-
D.
hasSeafloorAge
Indicates the age of a specified portion of the seafloor relative to a given time or reference point.
-
E.
olderRockUnit
Indicates that one rock unit formed earlier in geological time and therefore predates another rock unit.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605b710ec8190a84765aee7ba31e1 |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:02 a.m.