Triple
T21871596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABWH |
E540013
|
entity |
| Predicate | performedRepertoireFrom |
P139888
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [ABWH, performedRepertoireFrom, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedRepertoireFrom Context triple: [ABWH, performedRepertoireFrom, Yes]
-
A.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
B.
performsMusicFrom
Indicates that one entity presents or executes a musical work that originates from or was created by another entity.
-
C.
originalPerformanceFor
Indicates that one entity is the original performance or execution from which another related version, recording, or representation is derived.
-
D.
repertoireSource
chosen
Indicates that one entity serves as the origin or provider of the material, content, or items that make up another entity’s repertoire.
-
E.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f3368d488190a37224b587858ab0 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:58 p.m.