Triple
T19457410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | burczybas |
E486768
|
entity |
| Predicate | functionInEnsemble |
P30862
|
FINISHED |
| Object | rhythmic accompaniment |
—
|
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: rhythmic accompaniment | Statement: [burczybas, functionInEnsemble, rhythmic accompaniment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInEnsemble Context triple: [burczybas, functionInEnsemble, rhythmic accompaniment]
-
A.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
B.
functionInSystem
chosen
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
C.
actualFunction
Indicates that something serves as the real, operative function or role performed in practice, as opposed to a nominal or theoretical one.
-
D.
functionInPractice
Indicates that an entity serves a particular role or performs a specific function in actual use or real-world practice.
-
E.
functionInBuilding
Indicates that a specific function, role, or use is carried out within a particular building.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c569a081908b5a71226345a929 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.