Triple
T26759833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adèle Varens |
E674768
|
entity |
| Predicate | literaryWorkSetting |
P45019
|
FINISHED |
| Object | 19th-century England |
—
|
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: 19th-century England | Statement: [Adèle Varens, literaryWorkSetting, 19th-century England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryWorkSetting Context triple: [Adèle Varens, literaryWorkSetting, 19th-century England]
-
A.
hasLiterarySetting
Indicates that a literary work is set in, or primarily takes place within, a particular location or environment.
-
B.
narrativeSettingOfWork
chosen
Indicates that a particular place, time, or context serves as the narrative setting in which a work’s story or events occur.
-
C.
placeOfSetting
Indicates the location or environment where an event, scene, or situation takes place.
-
D.
literaryWorkInStory
Indicates that one literary work is referenced, featured, or embedded within the narrative of another story.
-
E.
laterSettingOfFiction
Indicates that one fictional work is set chronologically later than another within a shared narrative or story world.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 3:57 a.m.