Triple
T16860095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunjevac |
E409886
|
entity |
| Predicate | hasEthnicSymbol |
P10282
|
FINISHED |
| Object | Bunjevac 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: Bunjevac folk costume | Statement: [Bunjevac, hasEthnicSymbol, Bunjevac folk costume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicSymbol Context triple: [Bunjevac, hasEthnicSymbol, Bunjevac folk costume]
-
A.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
-
B.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
C.
hasEthnicTarget
Indicates that an action, statement, or event is directed toward or targets a specific ethnic group.
-
D.
hasTraditionalSymbol
chosen
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
E.
hasCulturalIcon
Indicates that an entity is associated with or possesses a person, symbol, or object widely recognized as a significant representation of a particular 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b502bc048190baa5a83015407080 |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.