Triple
T6498481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | đàn bầu |
E148815
|
entity |
| Predicate | pitchControl |
P49048
|
FINISHED |
| Object | bending with flexible rod |
—
|
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: bending with flexible rod | Statement: [đàn bầu, pitchControl, bending with flexible rod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pitchControl Context triple: [đàn bầu, pitchControl, bending with flexible rod]
-
A.
pitchConvertedTo
Indicates that one pitch has been transformed or translated into another pitch or pitch representation.
-
B.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
C.
stripPitch
Indicates removing the pitch or tonal information from an audio signal or sound representation, leaving only non-pitch-related characteristics.
-
D.
regulationPitch
chosen
Indicates that an entity controls, adjusts, or maintains the pitch (e.g., frequency or perceived highness/lowness) of another entity or signal.
-
E.
tone
Indicates the characteristic attitude or emotional quality expressed in how something is communicated or presented.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:41 p.m.