Triple
T35775606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jermaine Stewart |
E1034280
|
entity |
| Predicate | performedAsDancerFor |
P172541
|
FINISHED |
| Object | Soul Train |
—
|
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: Soul Train | Statement: [Jermaine Stewart, performedAsDancerFor, Soul Train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedAsDancerFor Context triple: [Jermaine Stewart, performedAsDancerFor, Soul Train]
-
A.
touredAsDancerFor
Indicates that one entity traveled and performed as a dancer in the professional company or act of another entity.
-
B.
alsoDancedAs
Indicates that an entity performed under an additional dance name or identity besides their primary one.
-
C.
hasDancePerformancesBy
chosen
Indicates that one entity features or includes dance performances carried out by another entity.
-
D.
choreographedIn
Indicates that an entity (typically a choreographer or group) created or arranged the choreography for a performance, work, or event in a specified context or production.
-
E.
choreographedTo
Indicates that one action, movement, or sequence has been deliberately designed or arranged to align in timing, pattern, or structure with another.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 3, 2026, 4:06 p.m.