Triple
T200122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubla Khan |
E4085
|
entity |
| Predicate | rhymeScheme |
P8081
|
FINISHED |
| Object | irregular rhyme scheme |
—
|
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: irregular rhyme scheme | Statement: [Kubla Khan, rhymeScheme, irregular rhyme scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rhymeScheme Context triple: [Kubla Khan, rhymeScheme, irregular rhyme scheme]
-
A.
hasStressPattern
Indicates that an entity (such as a word or phrase) follows a particular arrangement of stressed and unstressed units (e.g., syllables) in its pronunciation.
-
B.
numberOfStanzasInOriginalPoem
Indicates the total count of stanzas contained in the poem’s original version.
-
C.
numberOfOfficialStanzas
Indicates the total count of officially recognized stanzas associated with an entity, such as a song, poem, or anthem.
-
D.
commonlySungStanzas
Indicates that certain stanzas of a song or poem are those most frequently sung or performed in practice.
-
E.
hasSyllableCount
Indicates that one entity (typically a word or phrase) possesses a specific number of syllables given by the other entity.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25bcc6dc88190b8c24b485588dfe4 |
completed | Feb. 28, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69a25b4886b48190b46fd2244648a098 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25bc6ba208190aa8bec59d32f95fd |
completed | Feb. 28, 2026, 3:06 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.