Triple
T30662102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Know You Got Soul |
E780557
|
entity |
| Predicate | hasKeyFigureInPerformance |
P28040
|
FINISHED |
| Object | Bobby Byrd |
—
|
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: Bobby Byrd | Statement: [I Know You Got Soul, hasKeyFigureInPerformance, Bobby Byrd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyFigureInPerformance Context triple: [I Know You Got Soul, hasKeyFigureInPerformance, Bobby Byrd]
-
A.
hasKeyFigure
Indicates that an entity includes, involves, or is characterized by an important or central person relevant to it.
-
B.
hasPerformanceElement
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
C.
keyFigureDuring
Indicates that an entity played a central or highly influential role during a specified period, event, or process.
-
D.
hasSignaturePerformanceBy
Indicates that something features a standout or defining performance delivered by a particular performer.
-
E.
hasNotablePerformanceIn
chosen
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:31 p.m.