Triple
T28817292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anisian |
E727671
|
entity |
| Predicate | positionInTriassic |
P193301
|
FINISHED |
| Object | second stage of the Triassic Period |
—
|
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: second stage of the Triassic Period | Statement: [Anisian, positionInTriassic, second stage of the Triassic Period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTriassic Context triple: [Anisian, positionInTriassic, second stage of the Triassic Period]
-
A.
positionInJurassic
Indicates that something occupies or is assigned a specific place or role within the context of the Jurassic period.
-
B.
positionInDevonian
Indicates that one entity occupies a specific position, interval, or placement within the temporal span of the Devonian period.
-
C.
positionInSilurian
Indicates that something occupies a specific position or location within the Silurian geological period.
-
D.
positionInCambrian
Indicates the relative stratigraphic or temporal placement of something within the Cambrian period.
-
E.
positionInPermian
Indicates the relative ordering or placement of an element within a specific permutation.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: April 28, 2026, 6:33 a.m.