Triple
T3170001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny One Note |
E66304
|
entity |
| Predicate | isFrequentlyPerformedIn |
P22738
|
FINISHED |
| Object | revues |
—
|
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: revues | Statement: [Johnny One Note, isFrequentlyPerformedIn, revues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyPerformedIn Context triple: [Johnny One Note, isFrequentlyPerformedIn, revues]
-
A.
isFrequentlyPerformedOnTourBy
Indicates that an action or piece (such as a song, routine, or performance) is regularly and commonly carried out by an entity while they are on tour.
-
B.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
C.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
D.
isFrequentlyRecorded
Indicates that an entity is captured or documented many times within a given dataset, medium, or context.
-
E.
commonlyPerformedAs
chosen
Indicates that an action, behavior, or role is typically or frequently carried out in a particular manner, form, or context.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada64917e08190bf0466d2c5e43790 |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.