Triple
T37897122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormstout Brewery |
E945310
|
entity |
| Predicate | enemyCreatureType |
P66530
|
FINISHED |
| Object | hozen |
—
|
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: hozen | Statement: [Stormstout Brewery, enemyCreatureType, hozen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyCreatureType Context triple: [Stormstout Brewery, enemyCreatureType, hozen]
-
A.
enemyType
Indicates that one entity is classified as an enemy of a specified type or category in relation to another entity.
-
B.
enemyTypeOpposed
Indicates that one type of enemy is defined as being in opposition or conflict with another enemy type.
-
C.
enemyElement
Indicates that one entity is an opposing or adversarial counterpart to another within a given context or system.
-
D.
enemyCharacter
Indicates that one character is hostile or opposed to another, typically treating them as an adversary or foe.
-
E.
enemySpecies
chosen
Indicates that two species are in an antagonistic or hostile relationship, typically viewing each other as enemies.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:19 p.m.