Triple
T16721752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas J. Whitmore |
E406363
|
entity |
| Predicate | enemyInFiction |
P108467
|
FINISHED |
| Object | alien invaders |
—
|
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: alien invaders | Statement: [Thomas J. Whitmore, enemyInFiction, alien invaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyInFiction Context triple: [Thomas J. Whitmore, enemyInFiction, alien invaders]
-
A.
enemyCharacterIn
Indicates that a character is located within or present inside an enemy-controlled area, zone, or context.
-
B.
enemyCharacter
Indicates that one character is hostile or opposed to another, typically treating them as an adversary or foe.
-
C.
imaginaryEnemy
Indicates that one entity regards another as an enemy that exists only in imagination rather than in reality.
-
D.
laterEnemyOf
Indicates that one entity becomes an enemy of another at a later time, after not initially being in an antagonistic relationship.
-
E.
featuresAntagonistEntity
chosen
Indicates that the subject includes or involves an entity serving as an antagonist in the context of a narrative, interaction, or scenario.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38743750c81908a980372ad8f1a6a |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.