Triple
T32526474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemingford Home, Nebraska |
E831328
|
entity |
| Predicate | appearsInFiction |
P105687
|
FINISHED |
| Object | The Stand |
—
|
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: The Stand | Statement: [Hemingford Home, Nebraska, appearsInFiction, The Stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInFiction Context triple: [Hemingford Home, Nebraska, appearsInFiction, The Stand]
-
A.
appearsInFictionAs
Indicates that one entity is depicted or represented as a character, figure, or element within a fictional work or narrative.
-
B.
hasPlaceInFiction
Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
-
C.
usedInFictionalWork
chosen
Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
-
D.
livesInFiction
Indicates that one entity exists or resides within the fictional world or narrative setting created by another entity.
-
E.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 1, 2026, 1:01 a.m.