Triple
T24518931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relix Records |
E606460
|
entity |
| Predicate | hasFormerGratefulDeadMemberOnRoster |
P70532
|
FINISHED |
| Object | Tom Constanten |
—
|
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: Tom Constanten | Statement: [Relix Records, hasFormerGratefulDeadMemberOnRoster, Tom Constanten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerGratefulDeadMemberOnRoster Context triple: [Relix Records, hasFormerGratefulDeadMemberOnRoster, Tom Constanten]
-
A.
hasBandMember
Indicates that a musical group includes a specific individual as one of its members.
-
B.
featuresFormerBandMemberOf
chosen
Indicates that the subject entity includes, highlights, or presents an individual who was previously a member of the referenced band.
-
C.
originalBandMember
Indicates that a person was part of the band’s lineup at the time the band was first formed.
-
D.
hasBandmates
Indicates that two or more individuals are members of the same musical band or group at the same time.
-
E.
houseBandMember
Indicates that a person is a member of a house band, typically performing regularly as part of that resident musical group.
- 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.