Triple
T20925867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Riley |
E515340
|
entity |
| Predicate | isCommonlySungAt |
P32287
|
FINISHED |
| Object | folk clubs |
—
|
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: folk clubs | Statement: [John Riley, isCommonlySungAt, folk clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlySungAt Context triple: [John Riley, isCommonlySungAt, folk clubs]
-
A.
commonlySungTune
Indicates that a particular tune is frequently used as the melody for singing a given piece (such as lyrics, a song, or text).
-
B.
traditionallySungAfter
Indicates that one song or musical piece is customarily performed immediately following another in a cultural or traditional sequence.
-
C.
isOftenSungToTune
Indicates that one song or piece of text is frequently performed using the melody or musical setting of another.
-
D.
frequentlySings
Indicates that the subject engages in the act of singing on a regular or repeated basis.
-
E.
isTraditionallySungBy
chosen
Indicates that something, typically a song or chant, is customarily performed vocally by a particular person, group, or type of performer according to tradition.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f65200b08190ac208204a20f5a6a |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.