Triple
T4548184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disputatio pro declaratione virtutis indulgentiarum |
E110094
|
entity |
| Predicate | printedAs |
P23558
|
FINISHED |
| Object | pamphlet |
—
|
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: pamphlet | Statement: [Disputatio pro declaratione virtutis indulgentiarum, printedAs, pamphlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: printedAs Context triple: [Disputatio pro declaratione virtutis indulgentiarum, printedAs, pamphlet]
-
A.
printedOn
Indicates that something is produced or reproduced in physical form on a specified material, surface, or medium.
-
B.
printedBy
Indicates that one entity is produced or output in physical or digital form by another entity acting as the printer or printing agent.
-
C.
publishedAs
chosen
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
D.
projectionPrintType
Indicates the method or format by which a projection is printed or rendered (e.g., type or style of the projection output).
-
E.
printingAuthority
Indicates the entity responsible for producing or issuing a physical or printed version of another entity.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f272248190983ae439bd0ac0cc |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.