Triple
T7258024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angklung music |
E157771
|
entity |
| Predicate | instrumentClassification |
P75978
|
FINISHED |
| Object | idiophone-based ensemble |
—
|
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: idiophone-based ensemble | Statement: [Angklung music, instrumentClassification, idiophone-based ensemble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentClassification Context triple: [Angklung music, instrumentClassification, idiophone-based ensemble]
-
A.
tradeInstrument
Indicates a relationship where one entity is used as a financial or commercial instrument in a trade or transaction involving another entity.
-
B.
investmentType
Indicates the specific category or nature of an investment associated with an entity or transaction.
-
C.
notableAssetClass
Indicates that an entity is significantly associated with, or recognized for, a particular class of assets.
-
D.
assetClassesTraded
Indicates that an entity trades, deals in, or is involved with specific categories or classes of financial assets.
-
E.
commodityClass
Indicates that one entity is classified as belonging to a particular category or class of commodities in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb06acd881908a1735fbbbd5756f |
completed | March 27, 2026, 8:39 p.m. |
Created at: March 27, 2026, 2:57 p.m.