Triple
T37477679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke in Blue |
E931324
|
entity |
| Predicate | featuresMusicianshipRootedIn |
P205919
|
FINISHED |
| Object | New Orleans |
E3902
|
NE 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 | Statement: [Duke in Blue, featuresMusicianshipRootedIn, New Orleans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMusicianshipRootedIn Context triple: [Duke in Blue, featuresMusicianshipRootedIn, New Orleans]
-
A.
featuresMusician
Indicates that something (such as a work, event, or recording) prominently includes or showcases a particular musician.
-
B.
featuresPrimaryInstrument
Indicates that an entity is associated with the main or most prominent instrument used or highlighted in another entity (such as a work, performance, or recording).
-
C.
featuresRichHarmonies
Indicates that the subject contains or employs complex, layered, and sonically dense harmonic structures.
-
D.
featuresSongwriter
Indicates that a musical work includes or credits a particular person as its songwriter.
-
E.
featuresArtistFromGenre
Indicates that an entity includes or highlights an artist whose work belongs to a specified musical or artistic genre.
- F. None of above. chosen
Provenance (5 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40952bbfb88190b6fca3eb635d9605 |
completed | June 28, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.