Triple
T28530896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocket Poets Series |
E722038
|
entity |
| Predicate | typicalPhysicalSize |
P67473
|
FINISHED |
| Object | pocket-sized |
—
|
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: pocket-sized | Statement: [Pocket Poets Series, typicalPhysicalSize, pocket-sized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPhysicalSize Context triple: [Pocket Poets Series, typicalPhysicalSize, pocket-sized]
-
A.
typicalDimension
chosen
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
B.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
C.
typicalPanelSize
Indicates the usual or standard dimensions associated with a given panel.
-
D.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
E.
typicalDomainDimension
Indicates that a dimension is a standard or characteristic measurement typically associated with a given domain or context.
- 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_6a00b34364448190b8c9948d5a24d845 |
completed | May 10, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a00b2e4f13c819081bac7d763c414ad |
completed | May 10, 2026, 4:31 p.m. |
Created at: April 28, 2026, 3:28 a.m.