Triple
T968640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Royal Master |
E20893
|
entity |
| Predicate | styleComparedTo |
P278
|
FINISHED |
| Object | courtly tragicomedies of John Fletcher |
—
|
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: courtly tragicomedies of John Fletcher | Statement: [The Royal Master, styleComparedTo, courtly tragicomedies of John Fletcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleComparedTo Context triple: [The Royal Master, styleComparedTo, courtly tragicomedies of John Fletcher]
-
A.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
-
B.
isComparedTo
chosen
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
C.
styleInFull
Indicates that something is presented, written, or expressed in its complete, unabbreviated, or fully detailed form.
-
D.
relatedStyle
Indicates that one style is associated with, similar to, or derived from another style in some relevant way.
-
E.
hasHigherStyleThan
Indicates that one entity’s style is considered superior or more fashionable than another’s.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4481f508190adcf0a965a23862c |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a579888190afb489ac9fe8391c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.