Triple
T25929613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopkinsville Goblins incident of 1955 |
E653400
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American folklore event |
C44217
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: American folklore event Context triple: [Hopkinsville Goblins incident of 1955, instanceOf, American folklore event]
-
A.
American folklore character
An American folklore character is a legendary figure, often rooted in regional traditions and oral storytelling, that embodies cultural values, fears, or aspirations unique to the United States.
-
B.
urban legend
chosen
An urban legend is a widely circulated but unverified story, often presented as true, that reflects contemporary fears, morals, or curiosities within a culture.
-
C.
mythological event
A mythological event is a significant occurrence within a culture’s traditional stories or legends, often involving gods, heroes, or supernatural forces that explain natural phenomena, origins, or moral truths.
-
D.
fictionalEvent
A fictionalEvent represents an invented occurrence or happening within a narrative world, defined by its time, place, participants, and narrative significance.
-
E.
event in Native American history
A significant occurrence or series of actions involving Native American peoples that influenced their societies, cultures, territories, or relationships with other groups at a particular time in history.
- F. None of above.
Provenance (1 batch)
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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:36 a.m.