Triple
T5689078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLARITY AD |
E125383
|
entity |
| Predicate | safetyEndpointType |
P57698
|
FINISHED |
| Object | adverse events |
—
|
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: adverse events | Statement: [CLARITY AD, safetyEndpointType, adverse events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyEndpointType Context triple: [CLARITY AD, safetyEndpointType, adverse events]
-
A.
safetyCategory
Indicates the classification of something according to its level or type of safety.
-
B.
measuresSafetyUsing
Indicates that an entity evaluates or assesses safety by employing a specified method, tool, or standard.
-
C.
safetyProfile
Indicates the overall level and characteristics of risk or harm associated with something, typically summarizing how safe it is under specified conditions.
-
D.
hasEndpointType
chosen
Indicates that an entity has a specific type or classification assigned to one of its endpoints.
-
E.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.