Triple
T26166183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woe from Wit |
E654257
|
entity |
| Predicate | alternativeEnglishTitle |
P6688
|
FINISHED |
| Object | The Woes of Wit |
—
|
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 Woes of Wit | Statement: [Woe from Wit, alternativeEnglishTitle, The Woes of Wit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeEnglishTitle Context triple: [Woe from Wit, alternativeEnglishTitle, The Woes of Wit]
-
A.
alternateInterpretationOfTitle
Indicates that one title is an alternative interpretation or reading of another title, reflecting a different way the original title can be understood.
-
B.
titleInEnglish
chosen
Indicates that an entity’s title or name is given in the English language.
-
C.
alternateTitleOfAdaptedEdition
Indicates that a title is an alternative title specifically for an adapted edition of a work, rather than for the original version.
-
D.
languageOfAlternativeTitle
Indicates the language in which an alternative or variant title of an entity is expressed.
-
E.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 8:32 p.m.