Triple
T3216470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | There Is Nothin' Like a Dame |
E67408
|
entity |
| Predicate | sungByCharacters |
P14884
|
FINISHED |
| Object | sailors |
—
|
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: sailors | Statement: [There Is Nothin' Like a Dame, sungByCharacters, sailors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sungByCharacters Context triple: [There Is Nothin' Like a Dame, sungByCharacters, sailors]
-
A.
sungByCharacter
chosen
Indicates that a song or musical piece is performed vocally by a specific character.
-
B.
musicalCharacter
Indicates that one entity is a character or role that appears within the other entity, which is a musical work or production.
-
C.
sungAs
Indicates that something is performed or vocalized in the manner, role, or identity specified by another entity (e.g., a song or part being sung as a particular character, style, or version).
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
performedAsSingerIn
Indicates that an entity took part in a performance specifically in the role of a singer within a particular event, production, or context.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab096b588190b22e41a76263ae92 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.