Triple
T22756030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E. Flesher |
E562844
|
entity |
| Predicate | roleInBookProduction |
P16130
|
FINISHED |
| Object | printer of learned books |
—
|
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: printer of learned books | Statement: [E. Flesher, roleInBookProduction, printer of learned books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBookProduction Context triple: [E. Flesher, roleInBookProduction, printer of learned books]
-
A.
roleInFilmProduction
Indicates the specific function or responsibility an entity has within the making of a film.
-
B.
producerRole
Indicates that an entity serves in the role of producer for another entity, such as a work, product, or event.
-
C.
publisherRole
chosen
Indicates the specific function, capacity, or responsibility an entity has in relation to publishing a work or resource.
-
D.
bookWriter
Indicates that a person is the author who wrote the specified book.
-
E.
publisherOfWorkFeaturing
Indicates that one entity serves as the publisher responsible for releasing or distributing a work in which another specified entity is featured.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179bd22588190ac724a656194f5b9 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:25 p.m.