Triple
T19392341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSO Youth Choir |
E485098
|
entity |
| Predicate | hasArtisticLevel |
P136270
|
FINISHED |
| Object | high artistic level |
—
|
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: high artistic level | Statement: [LSO Youth Choir, hasArtisticLevel, high artistic level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisticLevel Context triple: [LSO Youth Choir, hasArtisticLevel, high artistic level]
-
A.
hasArtisticDiscipline
Indicates that one entity practices, specializes in, or is associated with a particular artistic discipline or field.
-
B.
hasArtisticGenre
Indicates that an entity (such as a work or creation) belongs to or is characterized by a particular artistic genre.
-
C.
hasArtisticActivity
Indicates that an entity engages in, participates in, or is associated with an artistic activity or creative practice.
-
D.
hasArtisticFocus
Indicates that an entity’s primary artistic attention, theme, or specialization is directed toward a particular subject, style, or medium.
-
E.
hasArtisticStrategy
Indicates that an entity employs or is associated with a particular artistic approach, method, or plan in creating or presenting art.
- F. None of above. chosen
Provenance (4 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b45caec81909dafdf66b361effd |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e50213571881909cd7543a43b51986 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.