Triple
T25338218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llangynwyd Middle |
E635334
|
entity |
| Predicate | isPartOfHistoricCoalMiningArea |
P80678
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Llangynwyd Middle, isPartOfHistoricCoalMiningArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfHistoricCoalMiningArea Context triple: [Llangynwyd Middle, isPartOfHistoricCoalMiningArea, true]
-
A.
locatedInFormerMiningArea
chosen
Indicates that an entity is situated within an area that was previously used for mining activities.
-
B.
locatedInHistoricMiningTown
Indicates that something is situated within a town historically associated with mining activity.
-
C.
hasCoalMiningHistory
Indicates that an entity has a past or ongoing involvement in coal mining activities or industry.
-
D.
isInCoalRegion
Indicates that an entity is located within a geographic region characterized by coal deposits, coal mining, or coal-related activities.
-
E.
partOfHistoricalArea
Indicates that one entity is located within or belongs to a designated historical area or heritage zone.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 1:32 p.m.