Triple
T4514946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreutzer Sonata |
E102131
|
entity |
| Predicate | workNumberInSet |
P57122
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Kreutzer Sonata, workNumberInSet, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInSet Context triple: [Kreutzer Sonata, workNumberInSet, 9]
-
A.
hasNumberWithinWork
Indicates that a specific number or numeric value is contained, referenced, or used within a particular work (such as a document, publication, or creative piece).
-
B.
workNumberInComposerOutput
Indicates that a specific work number appears in the output or catalog produced by a particular composer.
-
C.
setWorkIn
Indicates that an entity assigns or places a work, task, or project into a particular context, location, or setting.
-
D.
numberOfWorks
Indicates the total count of works associated with a given entity.
-
E.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5725745c81908bb462ba9537ae14 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:02 p.m.