Triple
T20276575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hythe Beds |
E503031
|
entity |
| Predicate | notableLithology |
P17895
|
FINISHED |
| Object | Kentish ragstone |
—
|
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: Kentish ragstone | Statement: [Hythe Beds, notableLithology, Kentish ragstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLithology Context triple: [Hythe Beds, notableLithology, Kentish ragstone]
-
A.
lithology
chosen
Indicates the type and characteristics of rock or sediment that compose a geological unit or layer.
-
B.
lithostratigraphicType
Indicates the specific lithostratigraphic classification or unit type that characterizes a rock body or stratigraphic unit within a geological framework.
-
C.
lithostratigraphicUsage
Indicates how a lithostratigraphic unit name is applied or used within a particular stratigraphic or geological classification context.
-
D.
notableQuarry
Indicates that an entity is a quarry that is particularly significant, well-known, or noteworthy in some context.
-
E.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
- 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.