Triple
T36957679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billy Blaze |
E914229
|
entity |
| Predicate | notableEnemySpecies |
P121133
|
FINISHED |
| Object | Vorticons |
E914230
|
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: Vorticons | Statement: [Billy Blaze, notableEnemySpecies, Vorticons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEnemySpecies Context triple: [Billy Blaze, notableEnemySpecies, Vorticons]
-
A.
enemySpecies
Indicates that two species are in an antagonistic or hostile relationship, typically viewing each other as enemies.
-
B.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
C.
notableBoss
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
-
D.
primaryAntagonistSpeciesFaced
chosen
Indicates the species that serves as the main opposing or enemy group confronted by a given entity.
-
E.
guardianSpecies
Indicates a relationship where one species serves as a protector or guardian for another species.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c3c186481908121c17a9f397680 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.