Triple
T2908253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muddy Mountains |
E63617
|
entity |
| Predicate | geologyPeriod |
P1327
|
FINISHED |
| Object | Mesozoic |
—
|
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: Mesozoic | Statement: [Muddy Mountains, geologyPeriod, Mesozoic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologyPeriod Context triple: [Muddy Mountains, geologyPeriod, Mesozoic]
-
A.
geologicalAge
chosen
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.
geochronologyMethod
Indicates the method or technique used to determine the age or chronological sequence of geological materials or events.
-
C.
supercontinentCyclePhase
Indicates the specific stage or phase of the long-term tectonic cycle in which supercontinents assemble, exist, and break apart.
-
D.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
E.
geologicalSystem
Indicates that one entity is a geological system (e.g., rock units, structures, or processes forming a coherent geologic framework) associated with or characterizing the other entity.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0d1dcf881909b3ae58d7cdfd9cd |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.