Triple
T36958113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell Knight |
E914238
|
entity |
| Predicate | sharesEnemyClassWith |
P202659
|
FINISHED |
| Object | Baron of Hell |
—
|
NE NERFINISHED |
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: Baron of Hell | Statement: [Hell Knight, sharesEnemyClassWith, Baron of Hell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesEnemyClassWith Context triple: [Hell Knight, sharesEnemyClassWith, Baron of Hell]
-
A.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
-
B.
sharesGameWithEnemy
Indicates that an entity participates in the same game or match as an opposing or enemy entity.
-
C.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
-
D.
sharesColliderWith
Indicates that two entities are configured to use or occupy the same physics collider, causing them to share collision detection behavior.
-
E.
sharesFateWith
Indicates that two or more entities are bound to experience the same outcome, destiny, or consequences.
- F. None of above. chosen
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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_6a00a74afb3c8190a274bf6681950aa3 |
completed | May 10, 2026, 3:42 p.m. |
Created at: May 3, 2026, 4:13 p.m.