Triple
T33658323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argylle |
E862281
|
entity |
| Predicate | leadActorForCharacterEllyConway |
P1507
|
FINISHED |
| Object | Bryce Dallas Howard |
—
|
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: Bryce Dallas Howard | Statement: [Argylle, leadActorForCharacterEllyConway, Bryce Dallas Howard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorForCharacterEllyConway Context triple: [Argylle, leadActorForCharacterEllyConway, Bryce Dallas Howard]
-
A.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
B.
leadActressCharacterName
Indicates the name of the character portrayed by the lead actress in a given work.
-
C.
portrayedBy
chosen
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
-
D.
leadActorForCharacterChantry
Indicates that one entity is the primary actor portraying the character Chantry in a performance or production.
-
E.
helenaBonhamCarterRole
Indicates the acting role or character portrayed by Helena Bonham Carter in 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:42 a.m.