Triple
T10975571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilisk |
E259360
|
entity |
| Predicate | eyeWeakness |
P25307
|
FINISHED |
| Object | Can be blinded |
—
|
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: Can be blinded | Statement: [Basilisk, eyeWeakness, Can be blinded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eyeWeakness Context triple: [Basilisk, eyeWeakness, Can be blinded]
-
A.
eyeCondition
chosen
Indicates that an entity has, experiences, or is characterized by a particular condition or disorder affecting the eyes.
-
B.
eyeAssociation
Indicates a relationship where one entity is associated with, linked to, or characterized by a particular eye or eye-related feature of another entity.
-
C.
eyeConditionCause
Indicates that one factor or event is the cause or contributing cause of a particular eye-related condition or disorder.
-
D.
eyeType
Indicates the specific kind or category of eyes an entity has, such as their form, structure, or visual style.
-
E.
coma
Indicates that an entity is in a state of prolonged unconsciousness and unresponsiveness, typically due to severe injury or illness.
- 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.