Triple
T32874929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enter the Dragon (voice, English version) |
E840898
|
entity |
| Predicate | hasDubActor |
P175851
|
FINISHED |
| Object | Keye Luke |
—
|
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: Keye Luke | Statement: [Enter the Dragon (voice, English version), hasDubActor, Keye Luke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDubActor Context triple: [Enter the Dragon (voice, English version), hasDubActor, Keye Luke]
-
A.
hasDUB
Indicates that one entity possesses or is associated with a deubiquitinating enzyme (DUB) activity or component.
-
B.
hasTwinActors
Indicates that two or more actors share a twin relationship, typically portraying twin characters or being treated as twins within a given context.
-
C.
hasStuntDouble
Indicates that one entity serves as a stunt double who performs dangerous or physically demanding actions on behalf of another entity.
-
D.
hasHumanCast
Indicates that a work or production features human performers as part of its cast.
-
E.
hasFictionalCoStar
Indicates that one entity appears as a co-star alongside another entity within a fictional work or narrative.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:18 a.m.