Triple
T2643284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toad Hall is taken over by weasels and stoats |
E62924
|
entity |
| Predicate | antagonists |
P17627
|
FINISHED |
| Object | weasels |
—
|
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: weasels | Statement: [Toad Hall is taken over by weasels and stoats, antagonists, weasels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antagonists Context triple: [Toad Hall is taken over by weasels and stoats, antagonists, weasels]
-
A.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
B.
hasAntagonistGroup
chosen
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
-
C.
antagonistOccupation
Indicates the role, job, or professional activity that the antagonist character performs.
-
D.
primaryEnemy
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
E.
archenemyOf
Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
- 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd8ff34988190ba9d69ce9d77c71d |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.