Triple
T9404466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death of Boris |
E226549
|
entity |
| Predicate | isFrequentlyAnalyzedIn |
P78157
|
FINISHED |
| Object | musicology literature |
—
|
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: musicology literature | Statement: [Death of Boris, isFrequentlyAnalyzedIn, musicology literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyAnalyzedIn Context triple: [Death of Boris, isFrequentlyAnalyzedIn, musicology literature]
-
A.
oftenAnalyzedIn
chosen
Indicates that something is frequently examined, studied, or evaluated within a particular context, field, or framework.
-
B.
isFrequentlyIncludedIn
Indicates that something is regularly or commonly contained or made part of something else.
-
C.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
D.
analyzes
Indicates that one entity systematically examines or evaluates another entity to understand its nature, structure, or components.
-
E.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c125dc8190a6438cf0ee23e7a9 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.