Triple
T26325385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cieszyn Silesia dispute |
E662237
|
entity |
| Predicate | concernsResource |
P93549
|
FINISHED |
| Object | coal deposits |
—
|
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 deposits | Statement: [Cieszyn Silesia dispute, concernsResource, coal deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsResource Context triple: [Cieszyn Silesia dispute, concernsResource, coal deposits]
-
A.
concernsView
Indicates that one entity is about, relates to, or is focused on a particular view, perspective, or way of seeing something.
-
B.
concernsProvision
chosen
Indicates a relationship where something is about, deals with, or relates to the supplying or making available of resources, services, or necessities.
-
C.
concernsEntity
Indicates that something (such as an action, issue, or piece of information) is about or relevant to a particular entity.
-
D.
subjectOfConcernFor
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
-
E.
concernsFeature
Indicates that something is about, relates to, or involves a particular feature.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 26, 2026, 10:30 p.m.