Triple
T37101307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimmeridge Clay Formation |
E918709
|
entity |
| Predicate | outcropsAt |
P168598
|
FINISHED |
| Object | Kimmeridge Bay |
—
|
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: Kimmeridge Bay | Statement: [Kimmeridge Clay Formation, outcropsAt, Kimmeridge Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcropsAt Context triple: [Kimmeridge Clay Formation, outcropsAt, Kimmeridge Bay]
-
A.
hasOutcropsAt
chosen
Indicates that a geological unit or feature is exposed at the Earth’s surface at a specified location.
-
B.
hasNamedOutcrop
Indicates that an entity is associated with a specific outcrop that has been given a distinct name.
-
C.
fossilsFoundAt
Indicates that fossil remains of an organism or taxon have been discovered at a particular location or site.
-
D.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
E.
notableRockFormation
Indicates that one entity is a rock formation that is especially remarkable, distinctive, or well-known in relation to the other entity.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.