Triple
T19850076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everybody must get stoned |
E476968
|
entity |
| Predicate | repetitionStyle |
P47229
|
FINISHED |
| Object | chant-like |
—
|
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: chant-like | Statement: [Everybody must get stoned, repetitionStyle, chant-like]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repetitionStyle Context triple: [Everybody must get stoned, repetitionStyle, chant-like]
-
A.
repetitionOf
Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
-
B.
repetitionPattern
Indicates a recurring structure or sequence in which an action, event, or element is repeated over time or across instances.
-
C.
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.
-
D.
repetitionCount
Indicates the number of times a particular event, action, or pattern is repeated within a given context.
-
E.
repetitionRole
Indicates that one entity serves a specific function or role within a repeated or recurring occurrence of another entity or event.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65867b5408190bbd12ca567c4705f |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.