Triple
T32998447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Folio of Beaumont and Fletcher (1647) |
E844293
|
entity |
| Predicate | primaryAuthorsRole |
P127695
|
FINISHED |
| Object | dramatists |
—
|
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: dramatists | Statement: [First Folio of Beaumont and Fletcher (1647), primaryAuthorsRole, dramatists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAuthorsRole Context triple: [First Folio of Beaumont and Fletcher (1647), primaryAuthorsRole, dramatists]
-
A.
primaryRoleFor
Indicates that one entity serves as the main or most important role or function for another entity.
-
B.
firstPublicationAuthor
Indicates that the subject is the author responsible for the first publication of the object.
-
C.
notableAuthorRole
chosen
Indicates that an entity holds a significant or distinguished role as an author in relation to another entity.
-
D.
authorRelationshipToMainSubject
Indicates the nature of the connection or role the author has in relation to the main subject.
-
E.
hasContributorRoleOfAuthor
Indicates that an entity participates as a contributor specifically in the role of an author in relation to 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:22 a.m.