Triple
T6655692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Ross Hyman |
E150935
|
entity |
| Predicate | bandRole |
P24740
|
FINISHED |
| Object | frontman of the Ramones |
—
|
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: frontman of the Ramones | Statement: [Jeffrey Ross Hyman, bandRole, frontman of the Ramones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bandRole Context triple: [Jeffrey Ross Hyman, bandRole, frontman of the Ramones]
-
A.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
B.
bandMemberContributor
Indicates that an entity contributes to a band in the role of a member, participating in its musical or creative activities.
-
C.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
bandLeader
Indicates that one entity serves as the leader or primary directing figure of a musical band that includes the other entity.
-
E.
band
Indicates that multiple entities join together to form a unified group, typically for a shared purpose or activity.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.