Triple
T22327921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baskerville’s Birmingham press |
E551947
|
entity |
| Predicate | paperFeatures |
P138932
|
FINISHED |
| Object | smooth wove paper surface |
—
|
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: smooth wove paper surface | Statement: [Baskerville’s Birmingham press, paperFeatures, smooth wove paper surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paperFeatures Context triple: [Baskerville’s Birmingham press, paperFeatures, smooth wove paper surface]
-
A.
paperQuality
Indicates the level or characteristics of quality associated with a paper or written work.
-
B.
paperFormat
Indicates the specific size or layout standard in which a paper document is produced or presented.
-
C.
paper1Type
Indicates that one entity is classified as the primary or first type/category of the associated paper entity.
-
D.
hasPaper
Indicates that an entity possesses, is associated with, or includes a specific paper (such as a document, publication, or written work) in some relevant context.
-
E.
usesPaperType
chosen
Indicates that one entity employs or operates with a specific type or category of paper.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15769fdb48190b84e0c019ab63579 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.