Triple
T34989636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thorn |
E1009343
|
entity |
| Predicate | inSetting |
P15599
|
FINISHED |
| Object | The Elder Scrolls universe |
—
|
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: The Elder Scrolls universe | Statement: [Thorn, inSetting, The Elder Scrolls universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inSetting Context triple: [Thorn, inSetting, The Elder Scrolls universe]
-
A.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
B.
indicatedSetting
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another entity.
-
C.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
-
D.
inductionSetting
Indicates the conditions or configuration under which an induction process or inductive operation is carried out.
-
E.
usedAsSettingFor
chosen
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.