Triple
T38561854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teckel |
E928095
|
entity |
| Predicate | hasTypicalHealthIssue |
P4720
|
FINISHED |
| Object | intervertebral disc disease |
—
|
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: intervertebral disc disease | Statement: [Teckel, hasTypicalHealthIssue, intervertebral disc disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalHealthIssue Context triple: [Teckel, hasTypicalHealthIssue, intervertebral disc disease]
-
A.
hasHealthConcern
chosen
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
B.
hasTypicalConditions
Indicates that something is associated with conditions or circumstances that are commonly or normally present for it.
-
C.
hasPossibleSymptom
Indicates that an entity (such as a condition or disease) may be associated with a particular symptom that can potentially occur.
-
D.
healthType
Indicates the specific category or classification of health status or condition associated with an entity.
-
E.
hasHealthCareCharacteristic
Indicates that an entity possesses a specific healthcare-related attribute, quality, or feature.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: May 3, 2026, 4:32 p.m.