Triple
T20382693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Neville (The Omega Man) |
E497878
|
entity |
| Predicate | adversaryType |
P15619
|
FINISHED |
| Object | nocturnal mutants |
—
|
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: nocturnal mutants | Statement: [Robert Neville (The Omega Man), adversaryType, nocturnal mutants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adversaryType Context triple: [Robert Neville (The Omega Man), adversaryType, nocturnal mutants]
-
A.
otherAdversary
Indicates that one entity is an adversary of another, distinct from any primary or previously identified adversary.
-
B.
modelsAdversary
Indicates that one entity represents, simulates, or formally characterizes another entity as an adversary within a given context or system.
-
C.
notableAdversary
Indicates that one entity is recognized as a significant or prominent opponent or rival of another entity.
-
D.
enemyType
chosen
Indicates that one entity is classified as an enemy of a specified type or category in relation to another entity.
-
E.
portraysAdversary
Indicates that one entity depicts or represents another entity as an opponent, enemy, or rival.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678b208ec8190a09bf5fd947a2a02 |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:27 a.m.