Triple
T31924242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swarajati “Rave Himagiri Kumari” |
E815056
|
entity |
| Predicate | commonlyAccompaniedBy |
P3100
|
FINISHED |
| Object | violin |
—
|
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: violin | Statement: [Swarajati “Rave Himagiri Kumari”, commonlyAccompaniedBy, violin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyAccompaniedBy Context triple: [Swarajati “Rave Himagiri Kumari”, commonlyAccompaniedBy, violin]
-
A.
oftenAccompaniedBy
chosen
Indicates that one entity is frequently found together with, occurs alongside, or is commonly associated in presence or use with another entity.
-
B.
usuallyAccompaniedBy
Indicates that one entity is commonly or habitually found together with, or occurs in the presence of, another entity.
-
C.
commonlyIdentifiedWith
Indicates that two entities are widely regarded or treated as the same or equivalent, even if they are formally distinct.
-
D.
mayBeAccompaniedBy
Indicates that one entity can optionally be present together with or alongside another entity.
-
E.
accompaniesTo
Indicates that one entity goes along with or escorts another entity to a specific destination or event.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 1, 2026, 12:03 a.m.