Triple
T33700151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archer |
E863432
|
entity |
| Predicate | isOneOfTwoCentralProtagonistsIn |
P32032
|
FINISHED |
| Object | The Beaux' Stratagem |
—
|
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: The Beaux' Stratagem | Statement: [Archer, isOneOfTwoCentralProtagonistsIn, The Beaux' Stratagem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneOfTwoCentralProtagonistsIn Context triple: [Archer, isOneOfTwoCentralProtagonistsIn, The Beaux' Stratagem]
-
A.
hasSecondaryProtagonist
Indicates that an entity (such as a work of fiction) features another character who serves as a secondary or supporting main protagonist alongside the primary one.
-
B.
hasSecondaryProtagonistOccupation
Indicates that a secondary protagonist in a narrative has a specific occupation or job role.
-
C.
coProtagonist
chosen
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
D.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
E.
hasChildProtagonist
Indicates that the work features a child as its main or central character.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:43 a.m.