Triple
T34601924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustus Snodgrass |
E888485
|
entity |
| Predicate | settingOfFictionalWorld |
P67881
|
FINISHED |
| Object | England |
—
|
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: England | Statement: [Augustus Snodgrass, settingOfFictionalWorld, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfFictionalWorld Context triple: [Augustus Snodgrass, settingOfFictionalWorld, England]
-
A.
periodOfFictionalSetting
Indicates the time period in which the events of a fictional work are set.
-
B.
settingOfFictionalLife
chosen
Indicates that a particular place or environment serves as the primary backdrop or context in which a fictional character’s life and experiences occur.
-
C.
associatedWithFictionalSetting
Indicates that an entity has a connection or relevance to a particular fictional setting or universe.
-
D.
basedInFictionalSetting
Indicates that an entity’s primary location or setting exists within a fictional or imaginary world rather than the real world.
-
E.
hasFictionalSettingElement
Indicates that something includes or is associated with a specific element or component of a fictional setting.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 2:03 a.m.