Triple
T13488141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weazel |
E318558
|
entity |
| Predicate | portrayedByAlsoKnownFor |
P110594
|
FINISHED |
| Object | Warwick Davis as Wicket W. Warrick |
—
|
LITERAL FINISHED |
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: Warwick Davis as Wicket W. Warrick | Statement: [Weazel, portrayedByAlsoKnownFor, Warwick Davis as Wicket W. Warrick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedByAlsoKnownFor Context triple: [Weazel, portrayedByAlsoKnownFor, Warwick Davis as Wicket W. Warrick]
-
A.
portrayedByAlsoPlays
Indicates that the actor who portrays a given character also plays another specified role or character.
-
B.
portrayedBy
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
-
C.
alsoPortrayedBy
Indicates that the same role or character is portrayed by an additional, different performer or actor.
-
D.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
E.
previouslyPortrayedBy
Indicates that the subject entity was portrayed in the past by the specified actor or performer.
- F. None of above. chosen
Provenance (4 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3b9b488190bb4e11424ff599c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:42 p.m.