Triple
T28414638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alison |
E719766
|
entity |
| Predicate | settingOfStoryInvolving |
P169851
|
FINISHED |
| Object | rural Wales |
—
|
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: rural Wales | Statement: [Alison, settingOfStoryInvolving, rural Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfStoryInvolving Context triple: [Alison, settingOfStoryInvolving, rural Wales]
-
A.
placeOfSetting
Indicates the location or environment where an event, scene, or situation takes place.
-
B.
storyTakesPlaceOver
Indicates that a story unfolds across or spans a specified duration of time.
-
C.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
-
D.
narrativeSettingOfWork
Indicates that a particular place, time, or context serves as the narrative setting in which a work’s story or events occur.
-
E.
workOfFictionSetting
chosen
Indicates that a work of fiction is set in, or primarily takes place within, a particular location, time, or environment.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 1:29 a.m.