Triple
T28817434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spinatum Zone |
E727677
|
entity |
| Predicate | belongsToEpoch |
P187155
|
FINISHED |
| Object | Early Jurassic Epoch |
—
|
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: Early Jurassic Epoch | Statement: [Spinatum Zone, belongsToEpoch, Early Jurassic Epoch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToEpoch Context triple: [Spinatum Zone, belongsToEpoch, Early Jurassic Epoch]
-
A.
mappingEpoch
Indicates the specific time period or version during which a particular mapping or correspondence between entities is defined or valid.
-
B.
isInEpoch
chosen
Indicates that one temporal entity (such as an event, time point, or interval) occurs within the bounds of a specified epoch or historical time period.
-
C.
epochReference
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
D.
isEpochBoundaryFor
Indicates that something marks or defines the transition point between two distinct epochs for another entity.
-
E.
DecEpoch
Indicates the specific point in time (epoch) at which a declination (Dec) measurement or coordinate value is defined or referenced.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 28, 2026, 6:33 a.m.