Triple
T37513594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider Forest |
E932574
|
entity |
| Predicate | hasPrimaryEnemyType |
P15619
|
FINISHED |
| Object | spider-type monsters |
—
|
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: spider-type monsters | Statement: [Spider Forest, hasPrimaryEnemyType, spider-type monsters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryEnemyType Context triple: [Spider Forest, hasPrimaryEnemyType, spider-type monsters]
-
A.
hasEnemiesTrait
Indicates that an entity possesses a characteristic or quality specifically related to having enemies.
-
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.
hasEnemies
Indicates that one entity is in an antagonistic or hostile relationship with another, considering them an enemy.
-
E.
enemyType
chosen
Indicates that one entity is classified as an enemy of a specified type or category 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.