Triple
T35324437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fireplace: TheNotTheOtherSide |
E1020137
|
entity |
| Predicate | artistCurrentStageName |
P63318
|
FINISHED |
| Object | Hodgy |
—
|
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: Hodgy | Statement: [Fireplace: TheNotTheOtherSide, artistCurrentStageName, Hodgy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artistCurrentStageName Context triple: [Fireplace: TheNotTheOtherSide, artistCurrentStageName, Hodgy]
-
A.
mainPerformerCurrentName
Indicates that the referenced name is the current official or primary name of the main performer associated with an event or work.
-
B.
touringArtistStageName
Indicates that the given name is the stage name used by an artist while touring or performing.
-
C.
hasRecordingArtistStageName
chosen
Indicates that a recording artist is known or performs under a particular stage name.
-
D.
associatedWithArtistStageName
Indicates that an entity has a relationship to, or is connected with, a particular artist’s stage name.
-
E.
frontmanStageName
Indicates that the specified stage name is used by the person who serves as the frontman (lead performer) of a musical group or band.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.