Triple
T32512461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uncle Moe’s Family Feedbag |
E830972
|
entity |
| Predicate | fictionalCityLocatedIn |
P49286
|
FINISHED |
| Object | Springfield |
—
|
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: Springfield | Statement: [Uncle Moe’s Family Feedbag, fictionalCityLocatedIn, Springfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalCityLocatedIn Context triple: [Uncle Moe’s Family Feedbag, fictionalCityLocatedIn, Springfield]
-
A.
partOfFictionalCity
Indicates that one entity is a component, area, or subdivision within a larger fictional city.
-
B.
cityOfFictionalLocation
Indicates that a fictional location is situated within or associated with a particular city.
-
C.
cityOfFictionalResidence
Indicates that a fictional character or entity resides in, or is associated with living in, a particular city within a narrative or fictional context.
-
D.
basedInFictionalLocation
chosen
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
E.
fictionalCityServed
Indicates that a fictional city is served by a particular service, facility, or infrastructure (such as transport, utilities, or institutions).
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 1, 2026, 1 a.m.