Triple
T36303880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawkette |
E893892
|
entity |
| Predicate | relatedAliasOfUser |
—
|
GENERATED |
| Object | Hawkeye (Kate Bishop) |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedAliasOfUser Context triple: [Hawkette, relatedAliasOfUser, Hawkeye (Kate Bishop)]
-
A.
notableUserAlias
Indicates that a user is known or recognized by a particular alternate name or alias.
-
B.
relatedIdentity
Indicates that two identities are connected or associated with each other in some meaningful way, such as being alternate, linked, or otherwise contextually related.
-
C.
hasAliasUser
chosen
Indicates that a user is known or referred to by an alternative name or identifier.
-
D.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
E.
associatedRecordLabelOfUser
Indicates that a particular record label is linked or connected to a given user.
- F. None of above.
Provenance (1 batch)
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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.