Triple
T21511107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horace Giddens |
E530720
|
entity |
| Predicate | hasHealthStatus |
P4720
|
FINISHED |
| Object | heart 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: heart disease | Statement: [Horace Giddens, hasHealthStatus, heart disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHealthStatus Context triple: [Horace Giddens, hasHealthStatus, heart disease]
-
A.
hasHealthCode
Indicates that an entity is associated with a specific health-related classification or status code.
-
B.
healthIndicator
Indicates a measure or signal that reflects the health status or condition of an entity.
-
C.
hasHealthConcern
chosen
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
D.
hasHealthArea
Indicates that an entity is associated with, or falls within the scope of, a particular health-related domain or area of concern.
-
E.
saluteStatus
Indicates the type or state of a salute being given or received between entities (e.g., whether, how, or in what manner one entity salutes another).
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea863b18819080e3ff249b10ec28 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.