Triple
T32553326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fido |
E832028
|
entity |
| Predicate | HelenRobinsonPortrayedBy |
P1507
|
FINISHED |
| Object | Carrie-Anne Moss |
—
|
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: Carrie-Anne Moss | Statement: [Fido, HelenRobinsonPortrayedBy, Carrie-Anne Moss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HelenRobinsonPortrayedBy Context triple: [Fido, HelenRobinsonPortrayedBy, Carrie-Anne Moss]
-
A.
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.
-
B.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
characterPortrayedIs
Indicates that one entity serves as the fictional or dramatic role that is depicted or played by another entity.
-
D.
actorForCharacter Helen Crane
Indicates that Helen Crane is the actor who portrays or performs the role of a given character.
-
E.
portrayedInOriginalProductionBy
Indicates that an entity (such as a role or character) was first brought to life or performed in the original production by a specific performer.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5c87f2481908ebd32c6dd30ec89 |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.