Triple
T1151790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belshazzar |
E23691
|
entity |
| Predicate | offeredPosition |
P26127
|
FINISHED |
| Object | third ruler in the kingdom |
—
|
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: third ruler in the kingdom | Statement: [Belshazzar, offeredPosition, third ruler in the kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredPosition Context triple: [Belshazzar, offeredPosition, third ruler in the kingdom]
-
A.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
B.
firstOffered
Indicates that one entity was the earliest or initial provider or proposer of something to another entity or context.
-
C.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
D.
offeredIn
Indicates that something is made available or provided within a particular context, setting, or medium.
-
E.
targetOfficeSought
Indicates the specific public or organizational office or position that an individual is seeking or running for.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bd0ab5f88190bb583fc63b4cc150 |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:44 p.m.