Triple
T19079976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penrhiwceiber |
E467000
|
entity |
| Predicate | hasNearbyCollierySite |
P38268
|
FINISHED |
| Object | former Penrhiwceiber Colliery |
—
|
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: former Penrhiwceiber Colliery | Statement: [Penrhiwceiber, hasNearbyCollierySite, former Penrhiwceiber Colliery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCollierySite Context triple: [Penrhiwceiber, hasNearbyCollierySite, former Penrhiwceiber Colliery]
-
A.
hasCoalMineNearby
Indicates that a location or entity is situated close to at least one coal mine.
-
B.
hasNearbyFormerMiningCommunity
Indicates that an entity is located close to a community that previously hosted mining activities but is no longer an active mining site.
-
C.
hasNearbyMine
chosen
Indicates that one entity is located close to or in the vicinity of a mine associated with another entity.
-
D.
collieryNow
Indicates that an entity currently functions as, or is used as, a colliery (a coal mine or mining site) at the present time.
-
E.
collieryClosed
Indicates that a coal mine (colliery) has ceased operations and is no longer active.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e82ec08190873186ff51e89d86 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.