Triple
T38589359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rampart of Skulls |
E932417
|
entity |
| Predicate | settingRegionInLore |
P114636
|
FINISHED |
| Object | Icecrown |
—
|
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: Icecrown | Statement: [The Rampart of Skulls, settingRegionInLore, Icecrown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingRegionInLore Context triple: [The Rampart of Skulls, settingRegionInLore, Icecrown]
-
A.
setInFictionalizedRegionOf
Indicates that an event or narrative is located within a region that is a fictionalized or altered version of a real-world place.
-
B.
culturalRegionOfLore
Indicates that a particular cultural region is the primary setting, origin, or contextual background for a given body of lore or tradition.
-
C.
regionSetting
Indicates that an entity is configured to operate within, or is associated with, a specific geographic or logical region.
-
D.
fictionalSettingRegion
chosen
Indicates that a fictional setting is located within or associated with a specific geographic or administrative region.
-
E.
settledRegion
Indicates that an entity has established a lasting presence or habitation within a particular geographic region.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:32 p.m.