Triple
T27724571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baby... I'm Back! |
E699057
|
entity |
| Predicate | mainStarRole |
P166850
|
FINISHED |
| Object | Demond Wilson as Ray Ellis |
—
|
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: Demond Wilson as Ray Ellis | Statement: [Baby... I'm Back!, mainStarRole, Demond Wilson as Ray Ellis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStarRole Context triple: [Baby... I'm Back!, mainStarRole, Demond Wilson as Ray Ellis]
-
A.
leadRoleActor
chosen
Indicates that an actor performs a leading or principal role in a work or production.
-
B.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
C.
isPrimaryStarOf
Indicates that a star serves as the main or central stellar object in relation to a specified system, object, or context.
-
D.
mainStars
Indicates that the subject is the primary or leading performer(s) featured in the object work or production.
-
E.
replacesInLeadRole
Indicates that one entity takes over or substitutes for another entity in the primary or leading role within a given context or production.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 3:08 p.m.