Triple
T16736466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uzziah |
E406729
|
entity |
| Predicate | statusAfterLeprosy |
P124447
|
FINISHED |
| Object | leper until the day of his death |
—
|
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: leper until the day of his death | Statement: [Uzziah, statusAfterLeprosy, leper until the day of his death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterLeprosy Context triple: [Uzziah, statusAfterLeprosy, leper until the day of his death]
-
A.
statusAfterRescue
Indicates the condition or state an entity is in following a rescue event or operation.
-
B.
statusAfterExile
Indicates the condition or standing an entity has once a period of exile has ended.
-
C.
statusAfterLeak
Indicates the condition or state of an entity after a leak event has occurred.
-
D.
showsHealedPathologies
Indicates that an entity displays or reveals medical pathologies that have been healed or resolved.
-
E.
statusAfter680
Indicates that an entity’s status or condition holds or applies after the point identified as 680 (e.g., a time, event, or version marker).
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3a86848190a03f243dd1bdb899 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.