Triple
T10400462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1 Henry IV |
E245130
|
entity |
| Predicate | writtenInVerseForm |
P82742
|
FINISHED |
| Object | blank verse |
—
|
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: blank verse | Statement: [1 Henry IV, writtenInVerseForm, blank verse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenInVerseForm Context triple: [1 Henry IV, writtenInVerseForm, blank verse]
-
A.
writtenInMetre
chosen
Indicates that a piece of writing is composed using a specific metrical pattern or rhythmic structure.
-
B.
hasVerseStyle
Indicates that one entity is characterized by, or presented in, the verse style specified by another entity.
-
C.
poeticStructure
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used by another entity.
-
D.
hasLyricalForm
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
E.
poeticStyle
Indicates the stylistic or formal manner in which something is expressed in poetry, such as its structure, tone, and linguistic features.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9e2f11c8190b30695cba2975544 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:07 p.m.