Triple
T455180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Treatise on Probability |
E7216
|
entity |
| Predicate | hasReprint |
P6359
|
FINISHED |
| Object | Cambridge University Press edition |
—
|
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: Cambridge University Press edition | Statement: [A Treatise on Probability, hasReprint, Cambridge University Press edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReprint Context triple: [A Treatise on Probability, hasReprint, Cambridge University Press edition]
-
A.
hasPrintVersion
chosen
Indicates that one entity exists or is available as a printed or physical edition of another entity.
-
B.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
C.
laterRepublishedWith
Indicates that an existing work was republished at a later time in a modified or updated form specified by the related entity.
-
D.
printedBy
Indicates that one entity is produced or output in physical or digital form by another entity acting as the printer or printing agent.
-
E.
printedOn
Indicates that something is produced or reproduced in physical form on a specified material, surface, or medium.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef87cc7c8190a0fec933457821e2 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.