Triple
T26573025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Mine Workers v. Pennington |
E666874
|
entity |
| Predicate | concernedIndustry |
P167291
|
FINISHED |
| Object | coal industry |
—
|
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 industry | Statement: [United Mine Workers v. Pennington, concernedIndustry, coal industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernedIndustry Context triple: [United Mine Workers v. Pennington, concernedIndustry, coal industry]
-
A.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
B.
concernsMarket
Indicates a relationship where something is about, relates to, or is focused on a particular market or set of markets.
-
C.
supportedIndustry
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
-
D.
industryExposure
Indicates the extent to which an entity is involved in, affected by, or financially linked to a particular industry or set of industries.
-
E.
concernsBusinessType
Indicates that something is related or applicable to a particular type or category of business.
- F. None of above. chosen
Provenance (4 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 27, 2026, 1:59 a.m.