Triple
T2684431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feodor III of Russia |
E57448
|
entity |
| Predicate | health |
P33305
|
FINISHED |
| Object | suffered from chronic illness |
—
|
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: suffered from chronic illness | Statement: [Feodor III of Russia, health, suffered from chronic illness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: health Context triple: [Feodor III of Russia, health, suffered from chronic illness]
-
A.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
B.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
C.
care
Indicates showing concern, attention, or responsibility for the well-being or needs of another entity.
-
D.
healthIndicator
chosen
Indicates a measure or signal that reflects the health status or condition of an entity.
-
E.
lifestyle
Indicates that an entity’s way of living or habitual behaviors are associated with, influence, or characterize another entity or outcome.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9edba5c8190b86d6cba0f1964e2 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.