Triple
T30732342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al McKay |
E782455
|
entity |
| Predicate | touringEnsembleLeaderOf |
P56624
|
FINISHED |
| Object | Al McKay Allstars |
—
|
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: Al McKay Allstars | Statement: [Al McKay, touringEnsembleLeaderOf, Al McKay Allstars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touringEnsembleLeaderOf Context triple: [Al McKay, touringEnsembleLeaderOf, Al McKay Allstars]
-
A.
bandLeader
chosen
Indicates that one entity serves as the leader or primary directing figure of a musical band that includes the other entity.
-
B.
houseBandLeader
Indicates that one entity serves as the leader of a house band associated with another entity (such as a venue, show, or organization).
-
C.
musicalEnsembleRole
Indicates the specific function or position an individual holds within a musical ensemble, such as performer, conductor, or composer.
-
D.
hasTouringRole
Indicates that an entity holds or performs a specific role or function within a touring context, such as a traveling production, show, or event.
-
E.
touringTeam
Indicates that a team is traveling to different locations to play matches or perform in a series of scheduled events.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68ee47d048190a0fe21f41556774f |
completed | May 2, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:37 p.m.