Triple
T18154297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulmonary valve |
E434587
|
entity |
| Predicate | isAssessedBy |
P1340
|
FINISHED |
| Object | echocardiography |
—
|
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: echocardiography | Statement: [Pulmonary valve, isAssessedBy, echocardiography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssessedBy Context triple: [Pulmonary valve, isAssessedBy, echocardiography]
-
A.
assessedBy
chosen
Indicates that an entity has been evaluated, examined, or judged by another entity (typically an agent or authority).
-
B.
isGradedBy
Indicates that an entity (such as an assignment, exam, or work) is evaluated and assigned a grade by another entity (such as a person, system, or organization).
-
C.
assessmentBasis
Indicates the underlying criteria, evidence, or method used as the foundation for making an assessment or evaluation between entities.
-
D.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
-
E.
requiresAssessmentBy
Indicates that one entity must be formally evaluated, reviewed, or judged by another specified entity before proceeding or being accepted.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de3a99c081908e9615072e62b02f |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.