Triple
T440306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ado Annie Carnes |
E10098
|
entity |
| Predicate | hasSongStyle |
P13181
|
FINISHED |
| Object | comic solo |
—
|
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: comic solo | Statement: [Ado Annie Carnes, hasSongStyle, comic solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSongStyle Context triple: [Ado Annie Carnes, hasSongStyle, comic solo]
-
A.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
B.
hasSpecialSong
Indicates that one entity possesses or is associated with a particular song that is unique, distinctive, or specially designated for it.
-
C.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
D.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
E.
hasSignatureSong
Indicates that an artist or performer is especially associated with a particular song that is widely recognized as their defining or most iconic work.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef2977888190a0590b2c1bd2f5da |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb9e6b0819093863959a6e5730a |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.