Triple
T30841449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 8 |
E785519
|
entity |
| Predicate | hasKeyVariant |
P140125
|
FINISHED |
| Object | B minor (Schubert) |
—
|
NE NERFINISHED |
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: B minor (Schubert) | Statement: [Symphony No. 8, hasKeyVariant, B minor (Schubert)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyVariant Context triple: [Symphony No. 8, hasKeyVariant, B minor (Schubert)]
-
A.
hasKeyVariants
chosen
Indicates that an entity is associated with one or more alternative key forms or versions that function as variants of a primary key.
-
B.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
C.
hasKeyExportVariety
Indicates that an entity has a primary or most important variety specifically intended for export.
-
D.
hasVariantConstant
Indicates that one entity is a specific constant-valued variant or fixed-value form of another entity.
-
E.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 8:45 p.m.