Triple
T27817498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mystery of Edwin Drood |
E702714
|
entity |
| Predicate | plannedNumberOfParts |
P51752
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [The Mystery of Edwin Drood, plannedNumberOfParts, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedNumberOfParts Context triple: [The Mystery of Edwin Drood, plannedNumberOfParts, 12]
-
A.
numberPlanned
chosen
Indicates that a specific quantity has been scheduled or intended for a future action or allocation.
-
B.
hasPlannedPart
Indicates that one entity includes another entity as a component or segment within a planned or scheduled whole.
-
C.
numberOfCompletedParts
Indicates the count of parts within a whole that have been finished or fully completed.
-
D.
plannedLength
Indicates the intended or scheduled duration or size of something as determined in advance, rather than its actual or realized extent.
-
E.
hasPartNumber
Indicates that one entity is assigned or associated with a specific part number used to identify it within a catalog, system, or inventory.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 5:46 p.m.