Triple
T26971733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ackermann’s Repository of Arts |
E679334
|
entity |
| Predicate | publisherBusinessType |
P641
|
FINISHED |
| Object | print shop |
—
|
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: print shop | Statement: [Ackermann’s Repository of Arts, publisherBusinessType, print shop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherBusinessType Context triple: [Ackermann’s Repository of Arts, publisherBusinessType, print shop]
-
A.
publisherType
chosen
Indicates the classification or category of a publisher in relation to a published work or entity.
-
B.
publishingSector
Indicates a relationship where an entity operates in, is associated with, or belongs to the publishing industry or market segment.
-
C.
publishingPlatform
Indicates that one entity serves as the medium or service through which another entity is published or made publicly available.
-
D.
ownedBookPublisher
Indicates that a book publisher is owned by a particular entity (such as a person, company, or organization).
-
E.
publishingOrganization
Indicates the organization responsible for issuing or making the referenced work publicly available.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 27, 2026, 6:40 a.m.