Triple
T12742728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorals |
E304526
|
entity |
| Predicate | folkCultureFeature |
P83906
|
FINISHED |
| Object | distinct highlander music |
—
|
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: distinct highlander music | Statement: [Gorals, folkCultureFeature, distinct highlander music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: folkCultureFeature Context triple: [Gorals, folkCultureFeature, distinct highlander music]
-
A.
cultureCharacteristic
Indicates that a particular trait, practice, or feature is a defining characteristic of a given culture.
-
B.
culturalElements
chosen
Indicates a relationship where certain elements (such as practices, symbols, or artifacts) belong to, express, or characterize a particular culture or cultural context.
-
C.
popularCultureTrait
Indicates that an entity exhibits a characteristic, behavior, or element that is commonly recognized or influential within popular culture.
-
D.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
E.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.