Triple
T25007104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vampire Sestina |
E625871
|
entity |
| Predicate | employsRepetitionOf |
P47229
|
FINISHED |
| Object | end-words |
—
|
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: end-words | Statement: [Vampire Sestina, employsRepetitionOf, end-words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employsRepetitionOf Context triple: [Vampire Sestina, employsRepetitionOf, end-words]
-
A.
usesRepetition
chosen
Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
-
B.
repetitionOf
Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
-
C.
causesRepetitionOf
Indicates that one entity brings about or is responsible for the recurrence or repeated occurrence of another entity or event.
-
D.
hasRepetition
Indicates that something occurs, appears, or is performed more than once, showing recurrence or repeated instances within a given context.
-
E.
repetitionPattern
Indicates a recurring structure or sequence in which an action, event, or element is repeated over time or across instances.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:05 a.m.