Triple
T30906143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinfonie in h-Moll |
E787304
|
entity |
| Predicate | hasCommonReferenceName |
P203570
|
FINISHED |
| Object | Schubert Symphony No. 8 in B minor |
E1933548
|
NE 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: Schubert Symphony No. 8 in B minor | Statement: [Sinfonie in h-Moll, hasCommonReferenceName, Schubert Symphony No. 8 in B minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonReferenceName Context triple: [Sinfonie in h-Moll, hasCommonReferenceName, Schubert Symphony No. 8 in B minor]
-
A.
hasCommonReference
Indicates that two or more entities share the same source, citation, or referential basis.
-
B.
hasCommonValue
Indicates that two or more entities share at least one identical value or attribute in common.
-
C.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
D.
hasFullNameReference
Indicates that one entity serves as a complete, explicit name or designation referring to another entity.
-
E.
hasTypeMemberCommonName
Indicates that an entity has a commonly used or informal name associated with a specific type or category of its members.
- F. None of above. chosen
Provenance (5 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01a534a8908190aa888d6be5deb824 |
completed | May 11, 2026, 9:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28fba07ed8819096aa282c77c559b8 |
completed | June 10, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a01a507c1f081909ff6abc5575db0bb |
completed | May 11, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_6a01a533c7d481909bdbdc13edd023f8 |
completed | May 11, 2026, 9:45 a.m. |
Created at: April 29, 2026, 8:50 p.m.