Triple
T33537443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Conroy as Batman |
E858971
|
entity |
| Predicate | portraysDualIdentity |
P192492
|
FINISHED |
| Object | Bruce Wayne |
—
|
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: Bruce Wayne | Statement: [Kevin Conroy as Batman, portraysDualIdentity, Bruce Wayne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysDualIdentity Context triple: [Kevin Conroy as Batman, portraysDualIdentity, Bruce Wayne]
-
A.
portraysDoubleRole
chosen
Indicates that a single performer or entity depicts or assumes two distinct roles within the same context or work.
-
B.
hasSecretIdentity
Indicates that an entity possesses an alternate, hidden identity that is not publicly known.
-
C.
portraysPersonAs
Indicates that one entity represents, depicts, or characterizes another person in a particular way or role.
-
D.
usesSuperheroIdentity
Indicates that an entity adopts or operates under a superhero persona or alias, rather than their ordinary identity.
-
E.
appearsInIdentity
Indicates that an entity is featured, referenced, or plays a role within a particular identity or identity-related context.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 1, 2026, 1:39 a.m.