Triple
T25024091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willie Fisher |
E626659
|
entity |
| Predicate | usedCoverIdentity |
P114813
|
FINISHED |
| Object | Rudolf Ivanovich Abel |
—
|
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: Rudolf Ivanovich Abel | Statement: [Willie Fisher, usedCoverIdentity, Rudolf Ivanovich Abel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCoverIdentity Context triple: [Willie Fisher, usedCoverIdentity, Rudolf Ivanovich Abel]
-
A.
usedBySuperheroIdentity
Indicates that a particular item, tool, or resource is utilized by a given superhero identity.
-
B.
characterCoverIdentity
chosen
Indicates that one character uses another identity as a cover or disguise, typically concealing their true identity.
-
C.
usesSuperheroIdentity
Indicates that an entity adopts or operates under a superhero persona or alias, rather than their ordinary identity.
-
D.
coverIdentityCreatedBy
Indicates that a cover identity was created by a particular agent or entity.
-
E.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44f68c3108190a84604ae5d015d84 |
completed | May 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:07 a.m.