Triple
T28898822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vic Viper |
E732898
|
entity |
| Predicate | enemyTypeFaced |
P121133
|
FINISHED |
| Object | aliens |
—
|
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: aliens | Statement: [Vic Viper, enemyTypeFaced, aliens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyTypeFaced Context triple: [Vic Viper, enemyTypeFaced, aliens]
-
A.
enemyType
Indicates that one entity is classified as an enemy of a specified type or category in relation to another entity.
-
B.
primaryAntagonistSpeciesFaced
chosen
Indicates the species that serves as the main opposing or enemy group confronted by a given entity.
-
C.
enemyForceType
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
D.
enemyCharacterIn
Indicates that a character is located within or present inside an enemy-controlled area, zone, or context.
-
E.
primaryEnemy
Indicates that one entity is the main or most significant adversary or opponent of another entity.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa5b40881908123b73bb40b1526 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:01 a.m.