Triple
T25201384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhys |
E631133
|
entity |
| Predicate | eyeFunction |
P115177
|
FINISHED |
| Object | ECHO-eye scanner |
—
|
NE NERFINISHED |
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: ECHO-eye scanner | Statement: [Rhys, eyeFunction, ECHO-eye scanner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eyeFunction Context triple: [Rhys, eyeFunction, ECHO-eye scanner]
-
A.
eyeFeatureObserved
Indicates that a specific characteristic or condition of the eye has been detected or recorded through observation.
-
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.
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.
eyeUsage
chosen
Indicates how an entity uses or engages its eyes in relation to another entity or activity.
-
E.
eyeLocation
Indicates the spatial position or placement of an eye relative to a reference object or coordinate system.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474b5e4408190b726bbd038fa3862 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:51 p.m.