Triple
T16441723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secernentea |
E399316
|
entity |
| Predicate | isMedicallyImportant |
P47123
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Secernentea, isMedicallyImportant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMedicallyImportant Context triple: [Secernentea, isMedicallyImportant, true]
-
A.
medicinalUse
Indicates that one entity is used as a treatment or remedy for a disease, condition, or health-related purpose affecting another entity.
-
B.
hasClinicalSignificance
chosen
Indicates that something (such as a finding, variant, or condition) has a meaningful impact or relevance in a clinical or medical context.
-
C.
medicalBackground
Indicates that an entity has a history of prior medical conditions, treatments, or health-related experiences relevant to its current state or context.
-
D.
isEmergencyMeasure
Indicates that an action, policy, or measure is taken specifically in response to an urgent or crisis situation, typically as a temporary or exceptional intervention.
-
E.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba91dc48190bc35db60f63d36d3 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.