Triple
T13913529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jehoahaz |
E334557
|
entity |
| Predicate | appointedAsKingBy |
P40147
|
FINISHED |
| Object | People of the land |
—
|
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: People of the land | Statement: [Jehoahaz, appointedAsKingBy, People of the land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsKingBy Context triple: [Jehoahaz, appointedAsKingBy, People of the land]
-
A.
appointedCrownPrinceBy
Indicates that one entity is formally designated as crown prince by another entity, typically an authority such as a monarch or governing body.
-
B.
crownedAs
chosen
Indicates that one entity is formally invested with a royal or ceremonial title or position by another entity or authority.
-
C.
successorAsTitularKing
Indicates that one entity becomes the next holder of a ceremonial or nominal kingship position previously held by another entity.
-
D.
appointedPrinceOfWalesBy
Indicates that one entity formally conferred upon another the title and role of Prince of Wales.
-
E.
royalAppointment
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27245c648190b2946845ce0fdbf8 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.