Triple
T36730542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Więcbork |
E907320
|
entity |
| Predicate | locatedInEthnoculturalRegion |
P74006
|
FINISHED |
| Object | Krajna |
E176384
|
NE 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: Krajna | Statement: [Więcbork, locatedInEthnoculturalRegion, Krajna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInEthnoculturalRegion Context triple: [Więcbork, locatedInEthnoculturalRegion, Krajna]
-
A.
isLocatedInMajorityEthnicRegion
Indicates that an entity is situated within a geographic region where a particular ethnic group constitutes the majority of the population.
-
B.
belongsToEthnographicRegion
chosen
Indicates that an entity is associated with or situated within a specific ethnographic region defined by shared cultural or ethnic characteristics.
-
C.
ethnicRegionOfFocus
Indicates that a particular ethnic group or ethnicity is the primary regional focus or subject of attention in a given context.
-
D.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
E.
locatedInTraditionalRegion
Indicates that an entity is situated within a specific traditional or historically recognized region.
- F. None of above.
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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a383f168c8190b4d33bdfe052eced |
completed | June 23, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.