Triple
T37459299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toshley |
E930877
|
entity |
| Predicate | hasHealth |
P181144
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Toshley, hasHealth, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHealth Context triple: [Toshley, hasHealth, 7]
-
A.
hasHealthCode
Indicates that an entity is associated with a specific health-related classification or status code.
-
B.
hasVitality
chosen
Indicates that an entity possesses a level or quality of life force, energy, or biological liveliness.
-
C.
hasHealthArea
Indicates that an entity is associated with, or falls within the scope of, a particular health-related domain or area of concern.
-
D.
healthAttribute
Indicates that one entity specifies or characterizes a particular health-related property, condition, or quality of another entity.
-
E.
hasHealthConcern
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4:17 p.m.