Triple
T18020972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tricuspid valve |
E431114
|
entity |
| Predicate | hasCusps |
P77182
|
FINISHED |
| Object | three |
—
|
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: three | Statement: [Tricuspid valve, hasCusps, three]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCusps Context triple: [Tricuspid valve, hasCusps, three]
-
A.
hasCusp
chosen
Indicates that one entity possesses or exhibits a pointed or projecting feature (a cusp) as part of its form or structure.
-
B.
hasInflectionPointsAt
Indicates that a function or curve has inflection points located at the specified positions or values.
-
C.
hasSaddle
Indicates that one entity possesses or is equipped with a saddle in relation to another entity or context.
-
D.
hasComplexPoints
Indicates that something possesses or includes points that are intricate, detailed, or composed of multiple interconnected parts.
-
E.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c1c5f88190a059ce4f86f7ed36 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.