Triple
T9317753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 52 in C minor (Haydn) |
E224165
|
entity |
| Predicate | relativePositionInOeuvre |
P19302
|
FINISHED |
| Object | middle-period symphony |
—
|
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: middle-period symphony | Statement: [Symphony No. 52 in C minor (Haydn), relativePositionInOeuvre, middle-period symphony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionInOeuvre Context triple: [Symphony No. 52 in C minor (Haydn), relativePositionInOeuvre, middle-period symphony]
-
A.
positionInAuthorOeuvre
chosen
Indicates the relative placement or order of a work within an author's overall body of work.
-
B.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
D.
positionInFiction
Indicates that one entity holds a specific role, status, or placement within a fictional work or narrative.
-
E.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd358b66148190a918c107490c8406 |
completed | April 1, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:38 p.m.