Triple
T32631824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellen Aim |
E834235
|
entity |
| Predicate | fictionalSettingOfStory |
P169851
|
FINISHED |
| Object | Richmond |
—
|
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: Richmond | Statement: [Ellen Aim, fictionalSettingOfStory, Richmond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalSettingOfStory Context triple: [Ellen Aim, fictionalSettingOfStory, Richmond]
-
A.
workOfFictionSetting
chosen
Indicates that a work of fiction is set in, or primarily takes place within, a particular location, time, or environment.
-
B.
fictionalStreetSetting
Indicates that an entity is set on or associated with a street that exists only within a fictional or imaginary context.
-
C.
basedInFictionalSetting
Indicates that an entity’s primary location or setting exists within a fictional or imaginary world rather than the real world.
-
D.
fictionalSettingRegion
Indicates that a fictional setting is located within or associated with a specific geographic or administrative region.
-
E.
associatedWithFictionalSetting
Indicates that an entity has a connection or relevance to a particular fictional setting or universe.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 1:07 a.m.