Triple
T38641858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish culture |
E938614
|
entity |
| Predicate | hasFolkCostume |
P66644
|
FINISHED |
| Object | Kraków regional 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: Kraków regional costume | Statement: [Polish culture, hasFolkCostume, Kraków regional costume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFolkCostume Context triple: [Polish culture, hasFolkCostume, Kraków regional costume]
-
A.
hasTraditionalAttire
chosen
Indicates that an entity possesses or is associated with clothing that is customary or traditional within a particular culture or community.
-
B.
traditionalDressVariant
Indicates that one traditional dress is a variant or localized form of another traditional dress within the same broader cultural or stylistic tradition.
-
C.
costume
Indicates that one entity is wearing, dressed in, or outfitted with the other entity as a costume.
-
D.
isCostumed
Indicates that an entity is wearing or otherwise adorned with a costume.
-
E.
nationalDress
Indicates that an item of clothing is recognized as the traditional or customary dress associated with a particular nation or culture.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 3, 2026, 4:32 p.m.