Triple
T22907949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drimolen Main Quarry |
E568503
|
entity |
| Predicate | stratigraphicAge |
P1327
|
FINISHED |
| Object | Early Pleistocene |
—
|
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: Early Pleistocene | Statement: [Drimolen Main Quarry, stratigraphicAge, Early Pleistocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stratigraphicAge Context triple: [Drimolen Main Quarry, stratigraphicAge, Early Pleistocene]
-
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.
geologicAgeRelativeTo
Indicates the relative chronological order between two geologic ages, specifying which one is older or younger without giving an absolute date.
-
C.
positionInGeologicTimescale
Indicates the relative placement of a time interval or event within the structured sequence of the geologic timescale.
-
D.
hasStratigraphicPosition
Indicates the relative position of one geological layer or unit within a stratigraphic sequence in relation to another.
-
E.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18071b9ec81908922d5f046f7930a |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.