Triple
T30357231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little G minor Symphony |
E772181
|
entity |
| Predicate | workNumberInMozartSymphonies |
P169089
|
FINISHED |
| Object | 25 |
—
|
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: 25 | Statement: [Little G minor Symphony, workNumberInMozartSymphonies, 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInMozartSymphonies Context triple: [Little G minor Symphony, workNumberInMozartSymphonies, 25]
-
A.
workNumberInMahlerSymphonies
Indicates the specific numbered position a work occupies within the sequence of Mahler’s symphonies.
-
B.
workNumberInBrucknerSymphonies
Indicates the specific ordinal number assigned to a work within the sequence of Bruckner’s symphonies.
-
C.
workNumberInComposerChamberMusic
Indicates that a specific work number is assigned to a composer's piece within their body of chamber music.
-
D.
numberOfSymphonies
Indicates the total count of symphonies associated with a given entity.
-
E.
workNumberWithinLondonSymphonies
Indicates the numerical position or identifier assigned to a work within the set of London Symphonies.
- F. None of above. chosen
Provenance (4 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6823fe8c48190a8911627f79dd949 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 7:57 p.m.