Triple
T30083822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir John in Love |
E764544
|
entity |
| Predicate | hasShakespeareSourceGenre |
P61875
|
FINISHED |
| Object | comedy |
—
|
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: comedy | Statement: [Sir John in Love, hasShakespeareSourceGenre, comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShakespeareSourceGenre Context triple: [Sir John in Love, hasShakespeareSourceGenre, comedy]
-
A.
hasShakespeareTheme
Indicates that something embodies, features, or is characterized by a theme originating from or strongly associated with Shakespeare’s works.
-
B.
hasSourceMaterialGenre
chosen
Indicates that the genre of the source material from which something is derived is specified.
-
C.
hasHamlet
Indicates that an entity possesses, contains, or is associated with a hamlet (a small settlement).
-
D.
hasStagePlayCounterpart
Indicates that one work has a corresponding or equivalent version in the form of a stage play.
-
E.
hasGivenGenreDefiningWork
Indicates that an entity has created or produced a work that is widely regarded as defining or fundamentally shaping a particular genre.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 7:03 p.m.