Triple
T17781662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean-Dominique Bauby |
E443913
|
entity |
| Predicate | eyeUsedForCommunication |
P59911
|
FINISHED |
| Object | left eye |
—
|
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: left eye | Statement: [Jean-Dominique Bauby, eyeUsedForCommunication, left eye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eyeUsedForCommunication Context triple: [Jean-Dominique Bauby, eyeUsedForCommunication, left eye]
-
A.
eyeUsage
Indicates how an entity uses or engages its eyes in relation to another entity or activity.
-
B.
usedToCommunicate
chosen
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
C.
eyeType
Indicates the specific kind or category of eyes an entity has, such as their form, structure, or visual style.
-
D.
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.
-
E.
eyeCharacteristic
Indicates a relationship where an entity possesses a specific attribute, feature, or quality of its eyes.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4872260b881908e77096500451816 |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.