Triple
T5831167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witallia |
E129349
|
entity |
| Predicate | likelyInstrumentation |
P1149
|
FINISHED |
| Object | panpipes |
—
|
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: panpipes | Statement: [Witallia, likelyInstrumentation, panpipes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyInstrumentation Context triple: [Witallia, likelyInstrumentation, panpipes]
-
A.
typicalInstrumentation
chosen
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
B.
originalInstrumentation
Indicates the relationship between a musical work and the specific instruments or ensemble for which it was initially scored or conceived.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
supportsDynamicInstrumentation
Indicates that an entity is capable of being instrumented or monitored at runtime without requiring recompilation or restart.
-
E.
installedInstrument
Indicates that one entity has placed or set up another entity as an instrument or device for use in a particular context or system.
- 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.