Triple
T4926675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashubians |
E110593
|
entity |
| Predicate | haveFolkCostume |
P42160
|
FINISHED |
| Object | Kashubian folk costume |
—
|
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: Kashubian folk costume | Statement: [Kashubians, haveFolkCostume, Kashubian folk costume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveFolkCostume Context triple: [Kashubians, haveFolkCostume, Kashubian folk costume]
-
A.
haveDistinctCostume
Indicates that the entities each possess a costume that is different from the others’ costumes.
-
B.
isCostumed
Indicates that an entity is wearing or otherwise adorned with a costume.
-
C.
traditionalDressVariant
Indicates that one traditional dress is a variant or localized form of another traditional dress within the same broader cultural or stylistic tradition.
-
D.
hasGarment
chosen
Indicates that one entity possesses, wears, or is associated with a particular garment.
-
E.
designedCostumesFor
Indicates that one entity created or planned the costumes used by another entity, typically for a performance, production, or event.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70354bd081909291a43439f42ed3 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.