Triple
T8400743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sedōka |
E198163
|
entity |
| Predicate | poeticMeter |
P30317
|
FINISHED |
| Object | 5-7-7 syllable pattern |
—
|
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: 5-7-7 syllable pattern | Statement: [sedōka, poeticMeter, 5-7-7 syllable pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poeticMeter Context triple: [sedōka, poeticMeter, 5-7-7 syllable pattern]
-
A.
poeticStructure
chosen
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.
-
B.
rhymeScheme
Indicates the pattern of end sounds in a sequence of lines, showing which lines rhyme with each other.
-
C.
typicalFootCountPerHemistich
Indicates the usual number of metrical feet found in each hemistich (half-line) of a verse.
-
D.
hasPoeticDevice
Indicates that one entity (typically a text or passage) employs or contains a specific poetic device present in the other entity.
-
E.
dominantMetreOf
Indicates that one metre (rhythmic pattern) is the primary or prevailing metrical structure used in another work, passage, or musical/poetic context.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb824da3148190bfa3a1abfdfa02de |
completed | March 31, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:04 p.m.