Triple
T7165447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnatic music |
E167056
|
entity |
| Predicate | droneInstrument |
P26810
|
FINISHED |
| Object | tambura |
—
|
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: tambura | Statement: [Carnatic music, droneInstrument, tambura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: droneInstrument Context triple: [Carnatic music, droneInstrument, tambura]
-
A.
droneCaste
Indicates a relationship where an entity belongs to or is classified as part of a drone caste within a social or hierarchical system.
-
B.
airbornePlatformFor
Indicates that one entity serves as an airborne platform or carrier used to support, transport, or deploy another entity.
-
C.
airCapability
Indicates that an entity possesses the ability or resources to operate or project power in the air (e.g., through aircraft, air defenses, or related systems).
-
D.
flyingDeviceDescribedAs
Indicates that a flying device is characterized or described in a particular way by some attribute, label, or description.
-
E.
coreInstrument
chosen
Indicates that an instrument plays a central or primary role in performing an action or achieving an outcome.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e832d2548190aacff0de80dbc268 |
completed | March 27, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.