Triple
T28883468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebel Ridge |
E732485
|
entity |
| Predicate | leadActorReplacement |
P127541
|
FINISHED |
| Object | Aaron Pierre |
—
|
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: Aaron Pierre | Statement: [Rebel Ridge, leadActorReplacement, Aaron Pierre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorReplacement Context triple: [Rebel Ridge, leadActorReplacement, Aaron Pierre]
-
A.
leadActorOfAdaptation
Indicates that a person is the main actor in a specific adaptation of a work (such as a film, series, or stage version).
-
B.
actsInSteadOf
chosen
Indicates that one entity performs an action or fulfills a role as a substitute or proxy for another entity.
-
C.
revivalLeadActor
Indicates that the subject is the lead actor in a revival (new production or version) of the related work or performance.
-
D.
leadActorParent
Indicates that one entity is the parent of the lead actor associated with another entity (such as a film, show, or performance).
-
E.
leadActorUntilDeath
Indicates that an individual served as the lead actor in a production or series continuously up until their death.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:47 a.m.