Triple
T25929640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopkinsville Goblins incident of 1955 |
E653400
|
entity |
| Predicate | creaturesMovementDescription |
P99141
|
FINISHED |
| Object | strange, almost weightless movements |
—
|
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: strange, almost weightless movements | Statement: [Hopkinsville Goblins incident of 1955, creaturesMovementDescription, strange, almost weightless movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creaturesMovementDescription Context triple: [Hopkinsville Goblins incident of 1955, creaturesMovementDescription, strange, almost weightless movements]
-
A.
describesMovement
Indicates that an entity undergoes or performs a change of position or location, capturing how it moves from one place or state to another.
-
B.
movementTypeDescribed
chosen
Indicates that a particular type or manner of movement is being specified or characterized.
-
C.
locomotion
Indicates movement or the ability to move from one place to another.
-
D.
typicalMovement
Indicates the usual or characteristic way in which an entity moves or is expected to move.
-
E.
movementDepicted
Indicates that some form of motion or change in position is visually represented or illustrated.
- 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_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 22, 2026, 8:36 a.m.