Triple
T25929639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopkinsville Goblins incident of 1955 |
E653400
|
entity |
| Predicate | creaturesEarDescription |
P44571
|
FINISHED |
| Object | large pointed ears |
—
|
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: large pointed ears | Statement: [Hopkinsville Goblins incident of 1955, creaturesEarDescription, large pointed ears]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creaturesEarDescription Context triple: [Hopkinsville Goblins incident of 1955, creaturesEarDescription, large pointed ears]
-
A.
hasEars
Indicates that an entity possesses ears as a physical feature.
-
B.
earDescription
chosen
Indicates a textual description of the characteristics or appearance of an entity’s ear or ears.
-
C.
hasEarTufts
Indicates that the subject possesses noticeable tufts of hair or feathers on its ears.
-
D.
earEvolution
Indicates how the structure, function, or complexity of an ear changes or develops over evolutionary time or across evolutionary lineages.
-
E.
usesElectroreceptionFor
Indicates that an entity detects and interprets electrical fields in its environment specifically for the associated purpose or activity.
- 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_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 22, 2026, 8:36 a.m.