Triple
T12671784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tell the Ones I Love |
E302700
|
entity |
| Predicate | mainGenreContext |
P20075
|
FINISHED |
| Object | American bluegrass music |
—
|
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: American bluegrass music | Statement: [Tell the Ones I Love, mainGenreContext, American bluegrass music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGenreContext Context triple: [Tell the Ones I Love, mainGenreContext, American bluegrass music]
-
A.
genreContext
chosen
Indicates the contextual genre or categorical style associated with an entity, such as the thematic or stylistic framework in which it is situated.
-
B.
commonGenre
Indicates that two entities share at least one genre in common.
-
C.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
-
D.
mainGenreShiftTo
Indicates a change in the primary genre classification of something from one main genre to another.
-
E.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.