Triple
T37180091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Decker |
E921168
|
entity |
| Predicate | hasPastMemberRole |
P201986
|
FINISHED |
| Object | Gym Class Heroes |
—
|
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: Gym Class Heroes | Statement: [Steve Decker, hasPastMemberRole, Gym Class Heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastMemberRole Context triple: [Steve Decker, hasPastMemberRole, Gym Class Heroes]
-
A.
hasNotableFormerMemberRole
Indicates that an entity has a role or position that was notably held by a former member of that entity.
-
B.
mayHavePriorRole
Indicates that an entity is allowed or expected to have held a specified role at some earlier time.
-
C.
hasFormerStaffMember
Indicates that an entity once had a person as a staff member, but that person is no longer employed there.
-
D.
hasFounderRoleInHistory
Indicates that an entity has held a founder role in the historical development or establishment of another entity.
-
E.
hasMemberWhoBecame
Indicates that a group or organization includes at least one member who later attained or transitioned into a specified role, status, or affiliation.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
| PDg | Predicate description generation | batch_6a003ffa64e48190b37cce7d1c939b78 |
completed | May 10, 2026, 8:21 a.m. |
Created at: May 3, 2026, 4:15 p.m.