Triple
T20759132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PreserVision |
E510926
|
entity |
| Predicate | oftenRecommendedBy |
P94529
|
FINISHED |
| Object | ophthalmologists |
—
|
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: ophthalmologists | Statement: [PreserVision, oftenRecommendedBy, ophthalmologists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenRecommendedBy Context triple: [PreserVision, oftenRecommendedBy, ophthalmologists]
-
A.
isOftenRecommendedBy
chosen
Indicates that one entity is frequently suggested or endorsed by another as a preferred or suitable choice.
-
B.
commendedBy
Indicates that an entity is praised or formally recognized by another entity for its actions, qualities, or achievements.
-
C.
commendedFor
Indicates that one entity has expressed praise or approval toward another entity specifically because of a particular action, quality, or achievement.
-
D.
recommendedIn
Indicates that one entity is suggested or endorsed within the context, content, or scope of another entity (such as a document, list, or recommendation source).
-
E.
canRecommend
Indicates that one entity is able or authorized to suggest or endorse another entity as suitable or preferable.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24751688190829f9d836abfb606 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:35 p.m.