Triple
T36303880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawkette |
E893892
|
entity |
| Predicate | relatedAliasOfUser |
P108483
|
FINISHED |
| Object | Hawkeye (Kate Bishop) |
E257930
|
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: Hawkeye (Kate Bishop) | Statement: [Hawkette, relatedAliasOfUser, Hawkeye (Kate Bishop)]
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 (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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39c3f50c4481909aef4c60f5be52a8 |
completed | June 22, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.