Triple
T37632628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Blow |
E936393
|
entity |
| Predicate | associatedWithRealName |
P9233
|
FINISHED |
| Object | Joe Hennig |
E936386
|
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: Joe Hennig | Statement: [Death Blow, associatedWithRealName, Joe Hennig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRealName Context triple: [Death Blow, associatedWithRealName, Joe Hennig]
-
A.
usedByRealName
Indicates that something (such as an alias, handle, or resource) is used by an entity identified by their real, legal name.
-
B.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
C.
notRealNameOf
Indicates that the referenced name is not the entity’s actual or official name (e.g., it is false, fabricated, or otherwise not the real name of that entity).
-
D.
basedOnRealPersonFor
Indicates that one entity is created, modeled, or inspired using a specific real person as its basis.
-
E.
realName
chosen
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41541e1eb08190b9f3caf2f6a51697 |
completed | June 28, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.