Triple
T17647765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mawmluh Cave |
E429405
|
entity |
| Predicate | GSSPAgeInYearsBeforePresent |
P6440
|
FINISHED |
| Object | 4200 |
—
|
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: 4200 | Statement: [Mawmluh Cave, GSSPAgeInYearsBeforePresent, 4200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GSSPAgeInYearsBeforePresent Context triple: [Mawmluh Cave, GSSPAgeInYearsBeforePresent, 4200]
-
A.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
B.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
C.
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.
-
D.
countsYearsFrom
chosen
Indicates a temporal relationship where the number of years is measured starting from a specified reference point or event.
-
E.
geologicAgeRelativeTo
Indicates the relative chronological order between two geologic ages, specifying which one is older or younger without giving an absolute date.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e3a5ad8819085d4bef669fc3152 |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:05 a.m.