Triple
T35101931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | String Quartet in B minor, Op. 33 No. 1 |
E1013041
|
entity |
| Predicate | nicknameOfSet |
P109144
|
FINISHED |
| Object | Russian quartets |
—
|
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: Russian quartets | Statement: [String Quartet in B minor, Op. 33 No. 1, nicknameOfSet, Russian quartets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameOfSet Context triple: [String Quartet in B minor, Op. 33 No. 1, nicknameOfSet, Russian quartets]
-
A.
nicknameOfObject
chosen
Indicates that one entity is used as an informal or alternative name (nickname) for another entity.
-
B.
nicknameOfProduct
Indicates that one term is used as an informal or alternative name (nickname) for a particular product.
-
C.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
D.
series2Nickname
Indicates that a particular nickname is used as an alternative name or informal title for a given series.
-
E.
partOfNicknameSeriesFor
Indicates that one nickname belongs to a series or set of related nicknames associated with the same entity.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.