Triple
T24856553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libiąż |
E622044
|
entity |
| Predicate | partOfHistoricalActivity |
P1451
|
FINISHED |
| Object | coal mining in Upper Silesian region |
—
|
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 in Upper Silesian region | Statement: [Libiąż, partOfHistoricalActivity, coal mining in Upper Silesian region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfHistoricalActivity Context triple: [Libiąż, partOfHistoricalActivity, coal mining in Upper Silesian region]
-
A.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
B.
historicalEventParticipation
Indicates that an entity took part in, contributed to, or was involved in a specific historical event.
-
C.
partOfHistoryOf
chosen
Indicates that one entity forms a component, episode, or contributing element within the historical development or narrative of another entity.
-
D.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
E.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 5:21 a.m.