Triple
T26088730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regenerating Degenerate |
E658058
|
entity |
| Predicate | hasAlliteration |
P60474
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Regenerating Degenerate, hasAlliteration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlliteration Context triple: [Regenerating Degenerate, hasAlliteration, yes]
-
A.
hasRhymingText
Indicates that two pieces of text share a rhyming relationship, typically ending with similar or identical sounds.
-
B.
hasRhymeSchemeFeature
Indicates that a poetic work exhibits a specific characteristic or pattern related to its rhyme scheme.
-
C.
hasRhymeLine
Indicates that one line of text rhymes with another line.
-
D.
hasRhymeStyle
Indicates that two linguistic elements share the same pattern or style of rhyming.
-
E.
hasPoeticDevice
chosen
Indicates that one entity (typically a text or passage) employs or contains a specific poetic device present in the other entity.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 26, 2026, 7:45 p.m.