Triple
T33297426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Effi Briest |
E852485
|
entity |
| Predicate | regionOfSetting |
P129506
|
FINISHED |
| Object | Pomerania |
—
|
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: Pomerania | Statement: [Effi Briest, regionOfSetting, Pomerania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfSetting Context triple: [Effi Briest, regionOfSetting, Pomerania]
-
A.
regionSetting
chosen
Indicates that an entity is configured to operate within, or is associated with, a specific geographic or logical region.
-
B.
regionID
Indicates that an entity is associated with, located in, or belongs to a specific geographic or administrative region identified by this ID.
-
C.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
D.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
E.
controlsRegion
Indicates that one entity has authoritative power or governing influence over a specified geographic or administrative region.
- 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_69f34966ed4c81908dc9dda82d8c7fe3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 1, 2026, 1:33 a.m.