Triple
T24887034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travis McCoy |
E622882
|
entity |
| Predicate | hasPartInMusicalGroup |
P118484
|
FINISHED |
| Object | vocals |
—
|
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: vocals | Statement: [Travis McCoy, hasPartInMusicalGroup, vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInMusicalGroup Context triple: [Travis McCoy, hasPartInMusicalGroup, vocals]
-
A.
playedInBand
Indicates that an entity was a member of and performed as part of a particular band.
-
B.
hasMusicalEnsemble
Indicates that one entity is associated with or includes a particular musical ensemble (such as a band, orchestra, or group) as part of its activities or composition.
-
C.
hasRoleInBand
chosen
Indicates that an entity holds a specific role or position within a band.
-
D.
hasMemberOfSongwritingBand
Indicates that an entity (typically a band or group) includes a specific member who participates in its songwriting activities.
-
E.
playedWithBandFrom
Indicates that an individual has performed as a member or guest with a musical band originating from a specified place or organization.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 5:25 a.m.