Triple
T29239029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How Can I Go On |
E741267
|
entity |
| Predicate | hasVocalRangeShowcaseFor |
P42895
|
FINISHED |
| Object | Freddie Mercury |
—
|
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: Freddie Mercury | Statement: [How Can I Go On, hasVocalRangeShowcaseFor, Freddie Mercury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalRangeShowcaseFor Context triple: [How Can I Go On, hasVocalRangeShowcaseFor, Freddie Mercury]
-
A.
isVocalShowcaseFor
chosen
Indicates that something serves as a performance or context specifically designed to highlight and display another entity’s vocal abilities.
-
B.
hasVocalRangeDescription
Indicates that an entity is associated with a textual description of its vocal range or vocal capabilities.
-
C.
vocalRange
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
-
D.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
-
E.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 12:30 p.m.