Triple
T33103500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelbyville |
E847122
|
entity |
| Predicate | hasFounderInFiction |
P97495
|
FINISHED |
| Object | Shelbyville Manhattan |
—
|
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: Shelbyville Manhattan | Statement: [Shelbyville, hasFounderInFiction, Shelbyville Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFounderInFiction Context triple: [Shelbyville, hasFounderInFiction, Shelbyville Manhattan]
-
A.
foundedByFictional
chosen
Indicates that an entity (such as an organization, place, or group) was established or created by a fictional character or entity.
-
B.
hasFictionalCoFounder
Indicates that an entity is associated with a co-founder who is a fictional or imaginary character rather than a real person.
-
C.
hasFounderCharacter
Indicates that an entity has a founder who possesses a specified character trait or set of personal qualities.
-
D.
hasFictionalAuthor
Indicates that one entity is the fictional or in-universe author of a work attributed to them.
-
E.
isFictionallyCreatedBy
Indicates that an entity is a fictional creation authored, invented, or brought into existence within a narrative by another entity.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 1, 2026, 1:26 a.m.