Triple
T25075684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paladin of Souls |
E628040
|
entity |
| Predicate | settingRegionInFiction |
P152884
|
FINISHED |
| Object | Chalion |
—
|
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: Chalion | Statement: [Paladin of Souls, settingRegionInFiction, Chalion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingRegionInFiction Context triple: [Paladin of Souls, settingRegionInFiction, Chalion]
-
A.
fictionalSettingRegion
Indicates that a fictional setting is located within or associated with a specific geographic or administrative region.
-
B.
setInFictionalizedRegionOf
Indicates that an event or narrative is located within a region that is a fictionalized or altered version of a real-world place.
-
C.
associatedWithRegionInFiction
chosen
Indicates that, within a fictional context, an entity is linked or connected to a particular region or geographic area.
-
D.
belongsToFictionalRegion
Indicates that an entity is located within, associated with, or under the jurisdiction of a fictional or imaginary geographic region.
-
E.
fictionalGeographicRegion
Indicates that a geographic region exists only in fiction or imagination rather than in the real world.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:21 a.m.