Triple
T38084272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luther’s 1520 reforming writings |
E950931
|
entity |
| Predicate | printingTechnologyUsed |
P8374
|
FINISHED |
| Object | movable-type printing press |
—
|
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: movable-type printing press | Statement: [Luther’s 1520 reforming writings, printingTechnologyUsed, movable-type printing press]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: printingTechnologyUsed Context triple: [Luther’s 1520 reforming writings, printingTechnologyUsed, movable-type printing press]
-
A.
printingLanguage
Indicates the language in which a text, document, or inscription is printed.
-
B.
printingMethod
chosen
Indicates the technique or process used to produce a printed item or image.
-
C.
printingSupport
Indicates that one entity provides or is compatible with printing capabilities or services for another entity.
-
D.
printingCenter
Indicates a relationship where one entity serves as the printing center (i.e., the facility or service that performs printing) for another entity.
-
E.
printingColor
Indicates that one entity uses or displays a specific color in the context of printing or printed output.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.