Triple
T37512867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver City |
E932557
|
entity |
| Predicate | opposedRealm |
P146425
|
FINISHED |
| Object | Burning Hells |
—
|
NE NERFINISHED |
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: Burning Hells | Statement: [Silver City, opposedRealm, Burning Hells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedRealm Context triple: [Silver City, opposedRealm, Burning Hells]
-
A.
opposedDomain
chosen
Indicates that two domains or areas of activity are in opposition or conflict with each other.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
theoryOpposed
Indicates that one theory stands in opposition to, or conflicts with, another theory.
-
D.
opposedAdministration
Indicates that one entity actively resisted, challenged, or worked against the governance, policies, or authority exercised by another entity or administration.
-
E.
opposedRegent
Indicates that one party actively resisted, challenged, or worked against the authority or actions of a regent.
- 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_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 3, 2026, 4:17 p.m.