Triple
T16736473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uzziah |
E406729
|
entity |
| Predicate | deathReferencedIn |
P25017
|
FINISHED |
| Object | Isaiah 6:1 |
—
|
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: Isaiah 6:1 | Statement: [Uzziah, deathReferencedIn, Isaiah 6:1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathReferencedIn Context triple: [Uzziah, deathReferencedIn, Isaiah 6:1]
-
A.
deathDescribedIn
chosen
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
B.
deathInterpretedAs
Indicates that one entity’s death is understood, framed, or interpreted in a particular way by another entity or within a given context.
-
C.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
D.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
E.
deathDescribedAs
Indicates that one entity characterizes, portrays, or refers to another entity’s death using a particular description, metaphor, or wording.
- 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_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. |
Created at: April 10, 2026, 5:20 a.m.