Triple
T23780242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Teschen |
E587791
|
entity |
| Predicate | associatedWithEthnicRegion |
P74006
|
FINISHED |
| Object | Polish Silesia |
—
|
NE NERFINISHED |
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: Polish Silesia | Statement: [Duke of Teschen, associatedWithEthnicRegion, Polish Silesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithEthnicRegion Context triple: [Duke of Teschen, associatedWithEthnicRegion, Polish Silesia]
-
A.
belongsToEthnographicRegion
chosen
Indicates that an entity is associated with or situated within a specific ethnographic region defined by shared cultural or ethnic characteristics.
-
B.
linkedToEthnicIdentity
Indicates a relationship where something is associated or connected with a particular ethnic identity.
-
C.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
D.
ethnoLinguisticRegionOf
Indicates that a region is defined or characterized by the shared ethnic and linguistic identity of the group associated with it.
-
E.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62ad61c8190a552e88bce2bad1c |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.