Triple
T18888187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back Home Again in Indiana |
E462011
|
entity |
| Predicate | featuredInRepertoireOf |
P3738
|
FINISHED |
| Object | New Orleans jazz bands |
—
|
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: New Orleans jazz bands | Statement: [Back Home Again in Indiana, featuredInRepertoireOf, New Orleans jazz bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInRepertoireOf Context triple: [Back Home Again in Indiana, featuredInRepertoireOf, New Orleans jazz bands]
-
A.
includedInStandardRepertoire
Indicates that something is part of the commonly accepted or regularly used set within a particular standard repertoire.
-
B.
notabilityInRepertoire
Indicates that a work holds particular significance or prominence within an entity’s repertoire.
-
C.
playsWith
Indicates that one entity engages in play or recreational activity together with another entity.
-
D.
repertoireIncludes
chosen
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
E.
playedWith
Indicates that one entity engaged in play or a playful activity together with another entity.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c478d8c481909291e7c471e5095a |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.