Triple
T33974884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RHINE |
E871107
|
entity |
| Predicate | hasSecondaryEndpoint |
P90082
|
FINISHED |
| Object | anatomical retinal outcomes |
—
|
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: anatomical retinal outcomes | Statement: [RHINE, hasSecondaryEndpoint, anatomical retinal outcomes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryEndpoint Context triple: [RHINE, hasSecondaryEndpoint, anatomical retinal outcomes]
-
A.
hasPrimaryEndpoint
Indicates that an entity designates another entity as its main or most important endpoint or target location.
-
B.
hasAlternativeEndPoint
Indicates that an entity can terminate at a different or optional end point instead of, or in addition to, its primary end point.
-
C.
hasSecondary
chosen
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
D.
hasSecondaryStation
Indicates that an entity is associated with an additional, subordinate, or backup station beyond its primary one.
-
E.
hasSecondaryCenter
Indicates that an entity possesses an additional, subordinate or auxiliary center beyond its primary center.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 1, 2026, 1:50 a.m.