Triple
T33015688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fafhrd and the Gray Mouser |
E844769
|
entity |
| Predicate | primarySettingWorld |
P14490
|
FINISHED |
| Object | Nehwon |
E1848818
|
NE 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: Nehwon | Statement: [Fafhrd and the Gray Mouser, primarySettingWorld, Nehwon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySettingWorld Context triple: [Fafhrd and the Gray Mouser, primarySettingWorld, Nehwon]
-
A.
primarySetting
Indicates that one entity serves as the main or central location, context, or environment in which the other entity’s events or activities primarily take place.
-
B.
primarySettingOf
chosen
Indicates that a location or context serves as the main or principal setting in which an entity (such as a story, event, or activity) takes place.
-
C.
primarySettingFeature
Indicates that a particular feature is the main or defining characteristic of a setting.
-
D.
worldType
Indicates the classification or category of world or environment that an entity is associated with.
-
E.
worldName
Indicates that an entity has or is associated with a specific world’s name.
- F. None of above.
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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34e5087a948190aba6b41b46b0af8a |
completed | June 19, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:23 a.m.