Triple
T28164271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geiseltal region |
E714981
|
entity |
| Predicate | geologicalAgeEvidence |
P1327
|
FINISHED |
| Object | Eocene |
—
|
NE NERFINISHED |
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: Eocene | Statement: [Geiseltal region, geologicalAgeEvidence, Eocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalAgeEvidence Context triple: [Geiseltal region, geologicalAgeEvidence, Eocene]
-
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.
hasGeologicalEvidenceOf
Indicates that there is geological data or features supporting the existence, occurrence, or impact of a specified phenomenon or event.
-
C.
geologicRecord
Indicates that one entity serves as a geologic record documenting the history, processes, or conditions of another entity over time.
-
D.
geologicalPeriodRelevance
Indicates that something is relevant to, associated with, or characteristic of a particular geological period.
-
E.
positionInGeologicTimescale
Indicates the relative placement of a time interval or event within the structured sequence of the geologic timescale.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 10:08 p.m.