Triple
T27864756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Stumble |
E704323
|
entity |
| Predicate | hasKeyRoleOf |
P101358
|
FINISHED |
| Object | lead guitarist: Freddie King |
—
|
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: lead guitarist: Freddie King | Statement: [The Stumble, hasKeyRoleOf, lead guitarist: Freddie King]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyRoleOf Context triple: [The Stumble, hasKeyRoleOf, lead guitarist: Freddie King]
-
A.
isKeyRole
chosen
Indicates that an entity holds a primary or critically important role within a given context or structure.
-
B.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
C.
hasKeyResponsibility
Indicates that an entity holds a primary duty or major obligation within a role, task, or context.
-
D.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
E.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 6:20 p.m.