Triple
T25829999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purlie Victorious |
E650635
|
entity |
| Predicate | revivalStar |
P116754
|
FINISHED |
| Object | Leslie Odom Jr. |
—
|
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: Leslie Odom Jr. | Statement: [Purlie Victorious, revivalStar, Leslie Odom Jr.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalStar Context triple: [Purlie Victorious, revivalStar, Leslie Odom Jr.]
-
A.
revivalStars
Indicates a relationship where one entity initiates, leads, or is central to a revival, renewal, or comeback of another entity.
-
B.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
C.
revivalHost
Indicates that one entity serves as the host or venue where a revival event, such as a renewed performance, series, or movement, takes place.
-
D.
revivalDirector
Indicates that one entity is the director responsible for staging or overseeing a revival (new production) of another entity, typically a work such as a play or performance.
-
E.
notableRevivalStar
chosen
Indicates that a person is a prominent or distinguished performer in a revival production of a work.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6019917c88190aeef4467dd7749c2 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 7:38 a.m.