Triple
T37592008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Kurast |
E935282
|
entity |
| Predicate | hasEnemiesType |
P195750
|
FINISHED |
| Object | demon enemies |
—
|
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: demon enemies | Statement: [Upper Kurast, hasEnemiesType, demon enemies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnemiesType Context triple: [Upper Kurast, hasEnemiesType, demon enemies]
-
A.
hasEnemies
chosen
Indicates that one entity is in an antagonistic or hostile relationship with another, considering them an enemy.
-
B.
hasUniqueEnemy
Indicates that an entity has exactly one distinct enemy with whom it is in an antagonistic relationship.
-
C.
hasOpposingForceType
Indicates that one force is characterized as being of a type that opposes or counteracts another force.
-
D.
hasCommonEnemies
Indicates that two or more entities share at least one enemy in common.
-
E.
hasEnemyLeader
Indicates that one entity is the primary opposing or adversarial leader in relation to 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:18 p.m.