Triple
T17453644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Todd Cook |
E424976
|
entity |
| Predicate | liveRole |
P120250
|
FINISHED |
| Object | touring musician |
—
|
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: touring musician | Statement: [Todd Cook, liveRole, touring musician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveRole Context triple: [Todd Cook, liveRole, touring musician]
-
A.
entertainmentRole
chosen
Indicates that an entity holds a specific function or position within an entertainment context (such as a role in a performance, production, or media work).
-
B.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
C.
cultRole
Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
-
D.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
-
E.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451406c748190b5ac6aacff7a3cc7 |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.