Triple
T35456560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grimethorpe, South Yorkshire |
E1024790
|
entity |
| Predicate | collieryName |
P116333
|
FINISHED |
| Object | Grimethorpe Colliery |
—
|
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: Grimethorpe Colliery | Statement: [Grimethorpe, South Yorkshire, collieryName, Grimethorpe Colliery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collieryName Context triple: [Grimethorpe, South Yorkshire, collieryName, Grimethorpe Colliery]
-
A.
collieryNow
Indicates that an entity currently functions as, or is used as, a colliery (a coal mine or mining site) at the present time.
-
B.
collieryClosed
Indicates that a coal mine (colliery) has ceased operations and is no longer active.
-
C.
collieryOpened
Indicates that a colliery (coal mine) was opened or began operations.
-
D.
mineName
chosen
Indicates that an entity has or is associated with a specific mine identified by a given name.
-
E.
coalMinedFrom
Indicates that a quantity or batch of coal has been extracted from a particular source location, such as a mine or geological deposit.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.