Triple
T25635187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pukkelpop |
E642678
|
entity |
| Predicate | lineupDiversity |
P14432
|
FINISHED |
| Object | multi-genre |
—
|
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: multi-genre | Statement: [Pukkelpop, lineupDiversity, multi-genre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineupDiversity Context triple: [Pukkelpop, lineupDiversity, multi-genre]
-
A.
diversity
chosen
Indicates the degree to which a set of entities differs along one or more dimensions such as type, attributes, or characteristics.
-
B.
lineupFeature
Indicates that an entity is included as a featured item or participant within a specific lineup or roster.
-
C.
peakDiversity
Indicates the point or condition at which diversity reaches its maximum level within a given context or system.
-
D.
styleDiversity
Indicates variation in the manner, form, or approach with which an entity presents, performs, or expresses something across different instances or contexts.
-
E.
centerOfDiversity
Indicates the location where a particular group, trait, or phenomenon exhibits its greatest variety or concentration of diversity.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa60db0c8190b5c615e6dc35264a |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:21 p.m.