Triple
T35807156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Phenom |
E1035130
|
entity |
| Predicate | hasNotableFeudWith |
P109978
|
FINISHED |
| Object | Shawn Michaels |
E640590
|
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: Shawn Michaels | Statement: [The Phenom, hasNotableFeudWith, Shawn Michaels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFeudWith Context triple: [The Phenom, hasNotableFeudWith, Shawn Michaels]
-
A.
feudedWith
chosen
Indicates a prolonged, often hostile conflict or rivalry between two entities.
-
B.
wasEnemyOf
Indicates that one entity regarded or interacted with another as an adversary or opponent, typically in a hostile or conflicting relationship.
-
C.
hasFriendEnemyRelationshipWith
Indicates a relationship where two entities are simultaneously connected as both friends and enemies, reflecting a mixed or ambivalent association between them.
-
D.
inspiredFeudWith
Indicates that one entity’s actions, ideas, or influence sparked or provoked a feud or ongoing conflict with another entity.
-
E.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbb359fc8190a88dbd1cf0cc0bd7 |
completed | June 23, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.