Triple
T36666094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skain’s Domain |
E905266
|
entity |
| Predicate | hasWorldbuilding |
P198094
|
FINISHED |
| Object | custom lore and history |
—
|
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: custom lore and history | Statement: [Skain’s Domain, hasWorldbuilding, custom lore and history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldbuilding Context triple: [Skain’s Domain, hasWorldbuilding, custom lore and history]
-
A.
worldbuildingFocus
Indicates that the primary creative or narrative emphasis is on constructing and exploring the setting, cultures, and underlying rules of a fictional world.
-
B.
worldbuildingFunction
Indicates the role or purpose something serves in constructing, shaping, or enriching an imagined world or setting.
-
C.
hasFictionalWorldType
Indicates that an entity is associated with, set in, or characterized by a particular type or category of fictional world.
-
D.
worldType
Indicates the classification or category of world or environment that an entity is associated with.
-
E.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
- F. None of above. chosen
Provenance (4 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69fec8adaa308190a9a276f8c36f15f0 |
completed | May 9, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:12 p.m.