Triple
T32965618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anton Koberger |
E843358
|
entity |
| Predicate | operatedPrintingPressIn |
P20247
|
FINISHED |
| Object | Nuremberg |
—
|
NE NERFINISHED |
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: Nuremberg | Statement: [Anton Koberger, operatedPrintingPressIn, Nuremberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedPrintingPressIn Context triple: [Anton Koberger, operatedPrintingPressIn, Nuremberg]
-
A.
usedPrintingPressAt
chosen
Indicates that one entity operated or made use of a printing press at, or in connection with, another entity (such as a place, time, or event).
-
B.
printingPressClosedIn
Indicates that a printing press ceased operations or was shut down in a specified location.
-
C.
operatedPublication
Indicates that one entity manages, runs, or oversees the functioning of a particular publication.
-
D.
printingOfWork
Indicates that one entity is a specific printing or print edition produced from a particular work.
-
E.
printingCenter
Indicates a relationship where one entity serves as the printing center (i.e., the facility or service that performs printing) for 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00474f08908190bc8ae3b320ec887b |
completed | May 10, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_6a0045dc3bd48190a9e0520f3ef3f067 |
completed | May 10, 2026, 8:46 a.m. |
Created at: May 1, 2026, 1:21 a.m.