Triple
T37452861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purbeck–Isle of Wight Fault Zone |
E930713
|
entity |
| Predicate | geologicalPeriodActivity |
P187642
|
FINISHED |
| Object | Jurassic |
—
|
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: Jurassic | Statement: [Purbeck–Isle of Wight Fault Zone, geologicalPeriodActivity, Jurassic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalPeriodActivity Context triple: [Purbeck–Isle of Wight Fault Zone, geologicalPeriodActivity, Jurassic]
-
A.
geologicalPeriodActive
chosen
Indicates that an entity was active or existed during a specified geological period.
-
B.
geologicalPeriodRelevance
Indicates that something is relevant to, associated with, or characteristic of a particular geological period.
-
C.
studiedGeologicalPeriod
Indicates that an entity has conducted study or research focused on a particular geological period.
-
D.
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.
-
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_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.