Triple
T10975566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilisk |
E259360
|
entity |
| Predicate | gazeEffect |
P16366
|
FINISHED |
| Object | Instant death on direct eye contact |
—
|
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: Instant death on direct eye contact | Statement: [Basilisk, gazeEffect, Instant death on direct eye contact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gazeEffect Context triple: [Basilisk, gazeEffect, Instant death on direct eye contact]
-
A.
gazeDirection
Indicates the direction in which an entity is looking or focusing its visual attention.
-
B.
eyeMigration
Indicates the movement or displacement of an eye (or eyes) from one position to another within an organism’s body or visual system.
-
C.
projectionEffect
Indicates the visual or spatial transformation produced when something is projected from one surface, medium, or viewpoint onto another.
-
D.
visualEffect
chosen
Indicates that one entity produces, modifies, or is associated with a particular visual effect on another entity or within a scene.
-
E.
eyeSide
Indicates the relative lateral position of an eye, specifying whether it is on the left or right side.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f4e888819097433271a2f45ff3 |
completed | April 9, 2026, 9:31 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:24 p.m.