Triple
T11392375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinfonia in F major (F.67) |
E269875
|
entity |
| Predicate | workNumberingScheme |
P70295
|
FINISHED |
| Object | F number |
—
|
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: F number | Statement: [Sinfonia in F major (F.67), workNumberingScheme, F number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberingScheme Context triple: [Sinfonia in F major (F.67), workNumberingScheme, F number]
-
A.
workNumbering
chosen
Indicates that a specific numbering or cataloging identifier is assigned to a work within a larger collection or system.
-
B.
workNumberingVariant
Indicates that one work serves as an alternative or variant numbering representation of another work within a numbering or cataloging system.
-
C.
standardNumberingScheme
Indicates that there is a specific, commonly accepted numbering system or convention being applied to identify or order the related entities.
-
D.
legalNumbering
Indicates that an entity has an officially assigned legal or regulatory identification number.
-
E.
numberingType
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d8001796f48190822526f52e3f0337 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.