Triple
T33087347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erwig |
E846675
|
entity |
| Predicate | healthStatusAtAccession |
P176107
|
FINISHED |
| Object | allegedly 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: allegedly ill | Statement: [Erwig, healthStatusAtAccession, allegedly ill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthStatusAtAccession Context triple: [Erwig, healthStatusAtAccession, allegedly ill]
-
A.
healthStatusAtProgramEntry
Indicates the health condition or status an entity had at the time they entered or started a particular program.
-
B.
healthIndicator
Indicates a measure or signal that reflects the health status or condition of an entity.
-
C.
hasHealthCode
Indicates that an entity is associated with a specific health-related classification or status code.
-
D.
healthStatusBeforeDeath
Indicates the condition or state of an entity’s health immediately prior to its death.
-
E.
preAccessionStatusOf
Indicates the status or condition of an entity prior to its formal accession or admission to another entity, group, or system.
- F. None of above. chosen
Provenance (4 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:26 a.m.