Triple
T13056276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "I'm Confessin' (That I Love You)" |
E327582
|
entity |
| Predicate | typicalPerformanceFormat |
P27645
|
FINISHED |
| Object | vocal with jazz ensemble |
—
|
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: vocal with jazz ensemble | Statement: ["I'm Confessin' (That I Love You)", typicalPerformanceFormat, vocal with jazz ensemble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceFormat Context triple: ["I'm Confessin' (That I Love You)", typicalPerformanceFormat, vocal with jazz ensemble]
-
A.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
B.
typicalPerformanceMode
chosen
Indicates the usual or most common way in which an entity performs an action or operates.
-
C.
typicalPerformanceSetting
Indicates the usual or most common context, venue, or environment in which a performance or activity typically takes place.
-
D.
typeOfPerformances
Indicates the kinds or categories of performances associated with or offered by an entity.
-
E.
typicalReleaseFormat
Indicates the usual or standard format in which something is released or published.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:58 p.m.