Triple
T30384494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The History Boys |
E772910
|
entity |
| Predicate | publisherOfPlayText |
P78728
|
FINISHED |
| Object | Faber and Faber |
—
|
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: Faber and Faber | Statement: [The History Boys, publisherOfPlayText, Faber and Faber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfPlayText Context triple: [The History Boys, publisherOfPlayText, Faber and Faber]
-
A.
publisherOfActingEdition
Indicates that an entity serves as the publisher responsible for issuing a specific acting edition of a work.
-
B.
publisherOfTextVersion
chosen
Indicates that an entity serves as the publisher responsible for a particular text version of a work.
-
C.
publisherOfScript
Indicates that an entity serves as the publisher responsible for issuing or distributing a particular script.
-
D.
publisherOfWorkFeaturing
Indicates that one entity serves as the publisher responsible for releasing or distributing a work in which another specified entity is featured.
-
E.
publisherOfWorks
Indicates that one entity serves as the publisher responsible for issuing or distributing the works created by 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 29, 2026, 8:01 p.m.