Triple
T25929633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopkinsville Goblins incident of 1955 |
E653400
|
entity |
| Predicate | creaturesDescribedAs |
P43047
|
FINISHED |
| Object | small beings |
—
|
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: small beings | Statement: [Hopkinsville Goblins incident of 1955, creaturesDescribedAs, small beings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creaturesDescribedAs Context triple: [Hopkinsville Goblins incident of 1955, creaturesDescribedAs, small beings]
-
A.
mentionsCreature
Indicates that one entity refers to or brings up a particular creature in some form of communication or content.
-
B.
speciesDescription
chosen
Indicates a textual description that characterizes or explains the features, traits, or nature of a species.
-
C.
usesCreature
Indicates that one entity employs, controls, or relies on a creature to perform an action or fulfill a function.
-
D.
rearsSpecies
Indicates that one entity raises, breeds, or cultivates individuals belonging to a particular species.
-
E.
featuresAnimalsFrom
Indicates that one entity includes, presents, or showcases animals originating from or associated with 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 22, 2026, 8:36 a.m.