Triple
T37626853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Hill mansion |
E936235
|
entity |
| Predicate | stateSongInspiration |
P198719
|
FINISHED |
| Object | "My Old Kentucky Home, Good-Night!" |
—
|
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: "My Old Kentucky Home, Good-Night!" | Statement: [Federal Hill mansion, stateSongInspiration, "My Old Kentucky Home, Good-Night!"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateSongInspiration Context triple: [Federal Hill mansion, stateSongInspiration, "My Old Kentucky Home, Good-Night!"]
-
A.
stateSong
Indicates that a particular song is officially designated as the state song of a given state or region.
-
B.
stateSongLyricsRevisedBy
Indicates that the lyrics of a state song have been modified or updated by a particular revising entity.
-
C.
hasOfficialStateSong
Indicates that a political entity is formally associated with a designated song recognized as its official state song.
-
D.
stateFolkSong
Indicates that a particular folk song is officially associated with, or designated as belonging to, a specific state.
-
E.
yearBecameStateSong
Indicates the specific year in which a song was officially designated as a state song.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
| PDg | Predicate description generation | batch_69feff703fec8190ab7d0633e0cc5459 |
completed | May 9, 2026, 9:33 a.m. |
Created at: May 3, 2026, 4:18 p.m.