Triple
T742192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocene |
E15266
|
entity |
| Predicate | timeScaleUnit |
P18870
|
FINISHED |
| Object | epoch on the geologic time scale |
—
|
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: epoch on the geologic time scale | Statement: [Holocene, timeScaleUnit, epoch on the geologic time scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeScaleUnit Context triple: [Holocene, timeScaleUnit, epoch on the geologic time scale]
-
A.
timeScaleType
Indicates the type or category of temporal scaling applied to an event, process, or measurement (e.g., real-time, accelerated, aggregated).
-
B.
timeUnitOfFrequency
Indicates the unit of time (e.g., day, week, month) in which a given frequency is measured or expressed.
-
C.
timescale
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
-
D.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- F. None of above. chosen
Provenance (4 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a60e286c81908787a41cf9b9f150 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fdaaf48190985f62acfc069508 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a5a35c68819082429755c046e9a7 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.