Triple
T6255623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnsley |
E140156
|
entity |
| Predicate | formerIndustrialCentreFor |
P67736
|
FINISHED |
| Object | coal mining |
—
|
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: coal mining | Statement: [Barnsley, formerIndustrialCentreFor, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerIndustrialCentreFor Context triple: [Barnsley, formerIndustrialCentreFor, coal mining]
-
A.
isIndustrialCenter
Indicates that a place functions as a major hub of industrial activity, production, or manufacturing within a region.
-
B.
partOfIndustrialRegion
Indicates that an entity is located within or belongs to a broader industrial region or industrially developed area.
-
C.
hasIndustrialHeritage
Indicates that an entity possesses or is associated with historically significant industrial sites, structures, or practices.
-
D.
hasIndustrialTown
Indicates that an entity possesses or is associated with a town characterized primarily by industrial activities or facilities.
-
E.
industrialFocus
chosen
Indicates a relationship where an entity is primarily concerned with, specialized in, or directed toward a particular industrial sector or area of industrial activity.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06363d6008190bf05e003b1f74497 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.