Triple
T26529219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoke thé |
E670772
|
entity |
| Predicate | performanceIncludes |
P170629
|
FINISHED |
| Object | 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: music | Statement: [Yoke thé, performanceIncludes, music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceIncludes Context triple: [Yoke thé, performanceIncludes, music]
-
A.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
B.
performanceAs
Indicates that one entity serves in a particular role, character, or capacity within a performance or presentation involving another entity.
-
C.
performanceBasis
Indicates that one entity’s performance is evaluated, determined, or justified on the basis of another specified factor, standard, or reference.
-
D.
performance
Indicates that one entity’s effectiveness, quality, or success in carrying out a task, function, or role is being evaluated or characterized in relation to some standard or expectation.
-
E.
performanceUse
Indicates that something is used, employed, or utilized in the course of performing an action, task, or function.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 1:34 a.m.