Triple
T28530905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocket Poets Series |
E722038
|
entity |
| Predicate | notableVolumeNumber |
P5040
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Pocket Poets Series, notableVolumeNumber, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVolumeNumber Context triple: [Pocket Poets Series, notableVolumeNumber, 4]
-
A.
notableVolume
Indicates that an entity is a significant or well-known volume (such as a book or written work) associated with another entity.
-
B.
notableNumber
Indicates that a number associated with an entity is distinguished or significant in some notable way (e.g., record-setting, symbolic, or otherwise remarkable).
-
C.
seriesVolumeNumber
chosen
Indicates the specific volume number assigned to an item within an ordered series.
-
D.
notableCount
Indicates the number of notable or distinguished items, entities, or instances associated with a given subject.
-
E.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a012efebda88190a90c8f650e4b1ee9 |
completed | May 11, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_6a01298cc604819087c836659c128926 |
completed | May 11, 2026, 12:57 a.m. |
Created at: April 28, 2026, 3:28 a.m.