Triple
T25929638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopkinsville Goblins incident of 1955 |
E653400
|
entity |
| Predicate | creaturesSkinDescription |
P24706
|
FINISHED |
| Object | shiny or metallic skin |
—
|
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: shiny or metallic skin | Statement: [Hopkinsville Goblins incident of 1955, creaturesSkinDescription, shiny or metallic skin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creaturesSkinDescription Context triple: [Hopkinsville Goblins incident of 1955, creaturesSkinDescription, shiny or metallic skin]
-
A.
fleshCharacteristic
Indicates that one entity has a particular property, quality, or attribute of its flesh (such as texture, color, or condition) in relation to another entity or value.
-
B.
fleshTexture
Indicates the tactile quality or surface feel of an entity’s flesh, such as how smooth, firm, soft, or coarse it is.
-
C.
fleshColor
chosen
Indicates the color or hue of an entity’s flesh or skin.
-
D.
hasSkin
Indicates that one entity possesses skin as a covering or outer tissue layer.
-
E.
describesAppearanceOf
Indicates that one entity provides information about the visual characteristics or outward look of 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_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 22, 2026, 8:36 a.m.