Triple
T21808468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochkov |
E538409
|
entity |
| Predicate | geologicalPeriodAssociated |
P43544
|
FINISHED |
| Object | Devonian |
—
|
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: Devonian | Statement: [Lochkov, geologicalPeriodAssociated, Devonian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalPeriodAssociated Context triple: [Lochkov, geologicalPeriodAssociated, Devonian]
-
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.
geologicRecord
Indicates that one entity serves as a geologic record documenting the history, processes, or conditions of another entity over time.
-
D.
geologicEraDominantRocks
Indicates that a particular type or group of rocks is the most characteristic or prevalent during a given geologic era.
-
E.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f078047ca88190a0efa4bc7f2faf80 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:53 p.m.