Triple
T37461410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xaril, Poisoned Mind |
E930925
|
entity |
| Predicate | relatedCardType |
P43530
|
FINISHED |
| Object | Toxin |
—
|
LITERAL 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: Toxin | Statement: [Xaril, Poisoned Mind, relatedCardType, Toxin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCardType Context triple: [Xaril, Poisoned Mind, relatedCardType, Toxin]
-
A.
relatedType
chosen
Indicates that one entity is connected to another through a specified type or category of relationship.
-
B.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
C.
relatedClassification
Indicates a relationship where one classification is associated with, linked to, or otherwise contextually connected to another classification.
-
D.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
E.
relatedArtifactType
Indicates the specific kind of relationship or linkage that one artifact has to another artifact (e.g., predecessor, successor, reference, dependency).
- F. None of above.
Provenance (3 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.