Triple
T20276598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hythe Beds |
E503031
|
entity |
| Predicate | hasSedimentaryStructures |
P40906
|
FINISHED |
| Object | cross-bedding |
—
|
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: cross-bedding | Statement: [Hythe Beds, hasSedimentaryStructures, cross-bedding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSedimentaryStructures Context triple: [Hythe Beds, hasSedimentaryStructures, cross-bedding]
-
A.
sedimentaryStructure
chosen
Indicates a relationship where a geological entity exhibits or is characterized by a particular sedimentary structure formed during deposition or shortly thereafter.
-
B.
hasStratigraphicFeature
Indicates a relationship in which a geological unit, site, or context contains, exhibits, or is associated with a particular stratigraphic feature (such as a layer, horizon, or boundary) within its stratigraphic sequence.
-
C.
hasSedimentaryBasin
Indicates that a geological region or area contains or is associated with a sedimentary basin.
-
D.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
E.
hasGeologicalEvidenceOf
Indicates that there is geological data or features supporting the existence, occurrence, or impact of a specified phenomenon or event.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675e3df68819096fb859bc92a0da1 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:35 a.m.