Triple
T32098673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twechar |
E819786
|
entity |
| Predicate | nearbyColliery |
P38268
|
FINISHED |
| Object | Twechar 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: Twechar Colliery | Statement: [Twechar, nearbyColliery, Twechar Colliery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyColliery Context triple: [Twechar, nearbyColliery, Twechar 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.
hasCoalMineNearby
Indicates that a location or entity is situated close to at least one coal mine.
-
C.
collieryClosed
Indicates that a coal mine (colliery) has ceased operations and is no longer active.
-
D.
hasNearbyFormerMiningCommunity
Indicates that an entity is located close to a community that previously hosted mining activities but is no longer an active mining site.
-
E.
hasNearbyMine
chosen
Indicates that one entity is located close to or in the vicinity of a mine associated with another 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 1, 2026, 12:26 a.m.