Triple
T33219526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heer Kaul |
E850381
|
entity |
| Predicate | healthStatusInPlot |
P175861
|
FINISHED |
| Object | terminally ill |
—
|
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: terminally ill | Statement: [Heer Kaul, healthStatusInPlot, terminally ill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthStatusInPlot Context triple: [Heer Kaul, healthStatusInPlot, terminally ill]
-
A.
healthIndicator
Indicates a measure or signal that reflects the health status or condition of an entity.
-
B.
healthStatusAtAccession
Indicates the condition or state of health an entity has at the time it is formally recorded, admitted, or added to a system or collection.
-
C.
healthStatusInNarrative
chosen
Indicates the health condition or state attributed to an entity within the context of a specific narrative or story.
-
D.
healthProxy
Indicates that one entity is authorized to make health-related or medical decisions on behalf of another entity.
-
E.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:30 a.m.