Triple
T5754858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Americans |
E126940
|
entity |
| Predicate | historicallyAssociatedIndustry |
P3008
|
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: [Polish Americans, historicallyAssociatedIndustry, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyAssociatedIndustry Context triple: [Polish Americans, historicallyAssociatedIndustry, coal mining]
-
A.
hasHistoricIndustry
chosen
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
B.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
C.
hadStateOwnershipOfIndustry
Indicates that a governing authority or state entity possessed ownership and control over a particular industry.
-
D.
foundingIndustry
Indicates the industry or sector in which an entity was originally founded or began its primary operations.
-
E.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02904dcf481909e4340a64ee1034e |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.