Triple
T6498487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | đàn bầu |
E148815
|
entity |
| Predicate | typicalTuning |
P30142
|
FINISHED |
| Object | around C3 to G3 open string |
—
|
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: around C3 to G3 open string | Statement: [đàn bầu, typicalTuning, around C3 to G3 open string]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTuning Context triple: [đàn bầu, typicalTuning, around C3 to G3 open string]
-
A.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
B.
tuning
Indicates the adjustment or calibration of something’s parameters or settings to achieve desired performance or behavior.
-
C.
tuningOfInstrument
chosen
Indicates the specific tuning configuration or pitch arrangement applied to a musical instrument.
-
D.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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.