Triple
T19767710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hephzibah |
E474800
|
entity |
| Predicate | spouseReignPeriod |
P137254
|
FINISHED |
| Object | reign of Hezekiah |
—
|
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: reign of Hezekiah | Statement: [Hephzibah, spouseReignPeriod, reign of Hezekiah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseReignPeriod Context triple: [Hephzibah, spouseReignPeriod, reign of Hezekiah]
-
A.
spouseReignName
Indicates the official reign name or title held by a person's spouse during their period of rule.
-
B.
spouseReignOverlap
Indicates that two spouses’ periods of reign as rulers overlapped in time.
-
C.
monarchSpouseReignStart
Indicates the date when a monarch’s spouse began their role as consort during the monarch’s reign.
-
D.
spouseIsLastIndependentRulerOf
Indicates that the subject’s spouse is recognized as the final ruler of a polity who governed independently, before loss of sovereignty or incorporation into another authority.
-
E.
spouseIsMonarchOf
Indicates that a person's spouse holds the position of monarch (ruler) of a specified country or territory.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65358fc3c8190867fea2a2c4e7594 |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:48 p.m.