Triple
T28270284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zarak |
E712826
|
entity |
| Predicate | leadActorForCharacter Zarak Khan |
P166476
|
FINISHED |
| Object | Victor Mature |
E131595
|
NE 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: Victor Mature | Statement: [Zarak, leadActorForCharacter Zarak Khan, Victor Mature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorForCharacter Zarak Khan Context triple: [Zarak, leadActorForCharacter Zarak Khan, Victor Mature]
-
A.
leadActorForCharacter Buz Murdock
Indicates that the specified person is the primary actor portraying the character Buz Murdock.
-
B.
worksForCharacterPlayedBy
Indicates that one character is employed by, or works under, another character who is portrayed by a specific actor.
-
C.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
D.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
-
E.
leadActorOfAdaptation
Indicates that a person is the main actor in a specific adaptation of a work (such as a film, series, or stage version).
- F. None of above. chosen
Provenance (5 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2870c0f1148190b39260b0200daa78 |
completed | June 9, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 27, 2026, 11:17 p.m.