Triple
T8712812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire Jurassic limestone belt |
E206817
|
entity |
| Predicate | hasQuarries |
P84029
|
FINISHED |
| Object | small local quarries |
—
|
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: small local quarries | Statement: [Yorkshire Jurassic limestone belt, hasQuarries, small local quarries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuarries Context triple: [Yorkshire Jurassic limestone belt, hasQuarries, small local quarries]
-
A.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
B.
hasMiningArea
Indicates that an entity possesses, controls, or is associated with a designated area where mining activities take place.
-
C.
hasMiningDistrict
Indicates that an entity possesses, contains, or is associated with a designated mining district within its domain or jurisdiction.
-
D.
hasMiningCommodity
Indicates that an entity is associated with, produces, or contains a specific mining-related commodity.
-
E.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
- F. None of above. chosen
Provenance (4 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c32aebc8190ba19299ce9a18efd |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c40c54819093d174a4203f9515 |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:35 p.m.