Triple
T22153206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midwich |
E547465
|
entity |
| Predicate | fictionalGeographyType |
P71480
|
FINISHED |
| Object | rural English village |
—
|
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 English village | Statement: [Midwich, fictionalGeographyType, rural English village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalGeographyType Context triple: [Midwich, fictionalGeographyType, rural English village]
-
A.
fictionalPlaceType
chosen
Indicates that a place is a fictional location and specifies what type or category of fictional place it is.
-
B.
fictionalGeographicRegion
Indicates that a geographic region exists only in fiction or imagination rather than in the real world.
-
C.
fictionalCountryLocation
Indicates that a fictional country is located within, or geographically associated with, a specified place or region.
-
D.
fictionalSettingRegion
Indicates that a fictional setting is located within or associated with a specific geographic or administrative region.
-
E.
stateOfFictionalLocation
Indicates that a fictional location is situated within or belongs to a particular state or state-like 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f5a740819093628386732b91a6 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.