Triple
T37632627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Blow |
E936393
|
entity |
| Predicate | associatedWithRingName |
P87629
|
FINISHED |
| Object | Michael McGillicutty |
E275202
|
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: Michael McGillicutty | Statement: [Death Blow, associatedWithRingName, Michael McGillicutty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRingName Context triple: [Death Blow, associatedWithRingName, Michael McGillicutty]
-
A.
associatedWithRing
Indicates that an entity has a connection or relationship with a specific ring, such as ownership, membership, or involvement.
-
B.
hasRingName
chosen
Indicates that an entity is associated with, or designated by, a specific ring name.
-
C.
memberRingName
Indicates that a specific name is assigned to a ring to which an entity belongs.
-
D.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
-
E.
ringsBy
Indicates that one entity creates or designs rings that are associated with, produced by, or attributed to another entity.
- 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_6a42e07b7ce08190a4defc5bb9fefd0b |
completed | June 29, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.