Triple
T24611360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee Waltz |
E609121
|
entity |
| Predicate | bSideOfPattiPageSingle |
P156746
|
FINISHED |
| Object | Boogie Woogie Santa Claus |
—
|
NE NERFINISHED |
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: Boogie Woogie Santa Claus | Statement: [Tennessee Waltz, bSideOfPattiPageSingle, Boogie Woogie Santa Claus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bSideOfPattiPageSingle Context triple: [Tennessee Waltz, bSideOfPattiPageSingle, Boogie Woogie Santa Claus]
-
A.
bSideOfSingleInUS
Indicates that one entity is the B-side track of a single that was released in the United States.
-
B.
singleSideOf
Indicates that one entity constitutes a single side or face of another entity, typically within a larger multi-sided structure or object.
-
C.
singleAorBside
Indicates that exactly one of the two related entities is on side A or side B, but not both simultaneously.
-
D.
singleSide
Indicates that the relationship or action involves only one side or participant, without a corresponding or reciprocal counterpart.
-
E.
bSideOfSingleByJeffersonAirplane
Indicates that something is the B-side track of a single released by Jefferson Airplane.
- F. None of above. chosen
Provenance (4 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:31 a.m.