Triple
T3131274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moshe Dayan |
E65417
|
entity |
| Predicate | eyeInjury |
P25307
|
FINISHED |
| Object | lost left eye in combat in 1941 |
—
|
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: lost left eye in combat in 1941 | Statement: [Moshe Dayan, eyeInjury, lost left eye in combat in 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eyeInjury Context triple: [Moshe Dayan, eyeInjury, lost left eye in combat in 1941]
-
A.
eyesPutOutBy
Indicates that one entity has caused another entity’s eyes to be damaged or removed, resulting in blindness.
-
B.
eyeCondition
chosen
Indicates that an entity has, experiences, or is characterized by a particular condition or disorder affecting the eyes.
-
C.
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.
-
D.
coma
Indicates that an entity is in a state of prolonged unconsciousness and unresponsiveness, typically due to severe injury or illness.
-
E.
eyeType
Indicates the specific kind or category of eyes an entity has, such as their form, structure, or visual style.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada54b0e688190b691771f17f4c721 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.