Triple
T35913056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marie Kimble Johnson |
E1038671
|
entity |
| Predicate | hasNotableSongScene |
P7326
|
FINISHED |
| Object | Tonight You Belong to Me |
E305223
|
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: Tonight You Belong to Me | Statement: [Marie Kimble Johnson, hasNotableSongScene, Tonight You Belong to Me]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSongScene Context triple: [Marie Kimble Johnson, hasNotableSongScene, Tonight You Belong to Me]
-
A.
hasNotableSongFeature
Indicates that one entity (typically a song) includes a significant or noteworthy contribution, appearance, or characteristic involving another entity.
-
B.
hasNotableSongType
Indicates that an entity is associated with a specific type or category of notable song.
-
C.
hasDanceSceneWith
Indicates that two entities participate together in a dance scene within the same context or work.
-
D.
notableScene
chosen
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
E.
hasNotableSongNumber
Indicates that an entity is associated with a specific song identified by its notable number or index within a collection or sequence.
- F. None of above.
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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ae2faecc819081260405036da5df |
completed | June 22, 2026, 3:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.