Triple
T3170000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny One Note |
E66304
|
entity |
| Predicate | isFrequentlyRecordedAs |
P21265
|
FINISHED |
| Object | jazz vocal standard |
—
|
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: jazz vocal standard | Statement: [Johnny One Note, isFrequentlyRecordedAs, jazz vocal standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyRecordedAs Context triple: [Johnny One Note, isFrequentlyRecordedAs, jazz vocal standard]
-
A.
isFrequentlyRecorded
Indicates that an entity is captured or documented many times within a given dataset, medium, or context.
-
B.
isFrequentlyDescribedAs
chosen
Indicates that something is often characterized or referred to using a particular description or set of attributes.
-
C.
isOftenRecordedWith
Indicates that one entity is frequently documented, captured, or logged at the same time as another entity.
-
D.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
E.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
- 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.