Triple
T928239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gentleman of Venice |
E20033
|
entity |
| Predicate | hasProseAndVerse |
P21485
|
FINISHED |
| Object | mixed verse and prose dialogue |
—
|
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: mixed verse and prose dialogue | Statement: [The Gentleman of Venice, hasProseAndVerse, mixed verse and prose dialogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProseAndVerse Context triple: [The Gentleman of Venice, hasProseAndVerse, mixed verse and prose dialogue]
-
A.
containsPoem
Indicates that one entity includes or holds a poem as part of its contents.
-
B.
hasVerseCount
Indicates that an entity (such as a text or section) is associated with a specific number of verses it contains.
-
C.
hasProseDialogue
Indicates that one entity contains or features spoken or conversational content expressed in prose form involving another entity.
-
D.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
E.
hasMultipleVerses
Indicates that something, typically a song, poem, or text, consists of more than one verse.
- F. None of above. chosen
Provenance (4 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b32de3cc81908a0ef885795677ff |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b29876348190a29f4ff9878074a5 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b2f4e3fc81908c8a2d1fbef9c5d2 |
completed | March 1, 2026, 9:43 p.m. |
Created at: March 1, 2026, 7:40 p.m.