Triple
T37452194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gypsum Spring Formation |
E930697
|
entity |
| Predicate | geologicTimeSpan |
P43544
|
FINISHED |
| Object | Bajocian |
—
|
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: Bajocian | Statement: [Gypsum Spring Formation, geologicTimeSpan, Bajocian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicTimeSpan Context triple: [Gypsum Spring Formation, geologicTimeSpan, Bajocian]
-
A.
geologicalAge
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.
geologicalRange
chosen
Indicates the span of geological time during which an entity (such as a taxon or formation) is known to have existed or been present.
-
C.
geologicTimeSubdivisionOf
Indicates that one geologic time unit is a constituent sub-division within a larger geologic time unit in the standard geologic timescale.
-
D.
positionInGeologicTimescale
Indicates the relative placement of a time interval or event within the structured sequence of the geologic timescale.
-
E.
geologicRecord
Indicates that one entity serves as a geologic record documenting the history, processes, or conditions of another entity over time.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.