Triple
T25929636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopkinsville Goblins incident of 1955 |
E653400
|
entity |
| Predicate | creaturesEyeDescription |
P142872
|
FINISHED |
| Object | large glowing eyes |
—
|
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 glowing eyes | Statement: [Hopkinsville Goblins incident of 1955, creaturesEyeDescription, large glowing eyes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creaturesEyeDescription Context triple: [Hopkinsville Goblins incident of 1955, creaturesEyeDescription, large glowing eyes]
-
A.
eyeCount
Indicates the number of eyes an entity has.
-
B.
hasEyes
Indicates that an entity possesses eyes as physical features.
-
C.
eyeCharacteristic
Indicates a relationship where an entity possesses a specific attribute, feature, or quality of its eyes.
-
D.
eyeType
Indicates the specific kind or category of eyes an entity has, such as their form, structure, or visual style.
-
E.
eyeFeatureObserved
chosen
Indicates that a specific characteristic or condition of the eye has been detected or recorded through observation.
- 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_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 22, 2026, 8:36 a.m.