Triple
T24548960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baby Won't You Please Come Home |
E607304
|
entity |
| Predicate | isStandardKey |
P156281
|
FINISHED |
| Object | B-flat major |
—
|
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: B-flat major | Statement: [Baby Won't You Please Come Home, isStandardKey, B-flat major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandardKey Context triple: [Baby Won't You Please Come Home, isStandardKey, B-flat major]
-
A.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
B.
isKeyCharacterIn
Indicates that an entity plays a central or primary role as a main or significant character within another entity, such as a story, game, or narrative work.
-
C.
isInKey
Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured context.
-
D.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
E.
hasStandardType
Indicates that something conforms to or is categorized under a defined standard classification or type.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8cc2838819087d3fd429f12b525 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:27 a.m.