Triple
T14486044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Good Soldier Švejk |
E359230
|
entity |
| Predicate | numberOfPlannedParts |
P51752
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [The Good Soldier Švejk, numberOfPlannedParts, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPlannedParts Context triple: [The Good Soldier Švejk, numberOfPlannedParts, 6]
-
A.
numberPlanned
chosen
Indicates that a specific quantity has been scheduled or intended for a future action or allocation.
-
B.
numberOfRulesPlanned
Indicates the planned or intended count of rules associated with an entity or process.
-
C.
numberOfCompletedParts
Indicates the count of parts within a whole that have been finished or fully completed.
-
D.
plannedComponent
Indicates that one entity is intended or scheduled to serve as a component or part of another entity in a planned or future configuration.
-
E.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924ee0f08190baf68318b41fa64d |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.