Triple
T5436003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balinese dance |
E122008
|
entity |
| Predicate | typicallyAccompaniedBy |
P3159
|
FINISHED |
| Object | gamelan music |
—
|
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: gamelan music | Statement: [Balinese dance, typicallyAccompaniedBy, gamelan music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyAccompaniedBy Context triple: [Balinese dance, typicallyAccompaniedBy, gamelan music]
-
A.
usuallyAccompaniedBy
chosen
Indicates that one entity is commonly or habitually found together with, or occurs in the presence of, another entity.
-
B.
oftenAccompaniedBy
Indicates that one entity is frequently found together with, occurs alongside, or is commonly associated in presence or use with another entity.
-
C.
accompaniedDuring
Indicates that one entity was present with and accompanied another entity during a specified event or time period.
-
D.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
E.
appearsAlongside
Indicates that two entities are present or occur together in the same context, setting, or instance.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:06 p.m.