Triple
T23940725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | độc huyền cầm |
E602773
|
entity |
| Predicate | pitchControlledBy |
P134169
|
FINISHED |
| Object | 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: flexible rod | Statement: [độc huyền cầm, pitchControlledBy, flexible rod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pitchControlledBy Context triple: [độc huyền cầm, pitchControlledBy, flexible rod]
-
A.
pitchDeterminedBy
chosen
Indicates that the pitch of one entity is defined or controlled by another specified factor or entity.
-
B.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
C.
pitchAlterationMechanism
Indicates the mechanism or method by which the pitch of a sound or signal is changed or controlled.
-
D.
governedByInstrument
Indicates that an action, process, or state is carried out, regulated, or controlled through the use of a specific instrument or tool.
-
E.
pitchConvertedTo
Indicates that one pitch has been transformed or translated into another pitch or pitch representation.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02a1b308190a2d101774b455417 |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:09 p.m.