Triple
T24078410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filter |
E596441
|
entity |
| Predicate | hasNotableTouringMember |
P91979
|
FINISHED |
| Object | Richard Patrick |
—
|
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: Richard Patrick | Statement: [Filter, hasNotableTouringMember, Richard Patrick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTouringMember Context triple: [Filter, hasNotableTouringMember, Richard Patrick]
-
A.
hasTouringMember
chosen
Indicates that an entity has a member who participates in its tours or live performances, typically as part of a traveling lineup.
-
B.
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.
-
C.
hasBandMember
Indicates that a musical group includes a specific individual as one of its members.
-
D.
hasTouringAct
Indicates that an entity (such as a venue, festival, or organization) features, hosts, or is associated with a touring performance act.
-
E.
hasNotablePerformerMembership
Indicates that an entity is or has been a distinguished or noteworthy member of a particular performer group, organization, or ensemble.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db1f4c98819089a0e470593baf5b |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:43 p.m.