Triple
T19433299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramesses I |
E486168
|
entity |
| Predicate | heldOfficeBeforeKingship |
P47324
|
FINISHED |
| Object | vizier |
—
|
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: vizier | Statement: [Ramesses I, heldOfficeBeforeKingship, vizier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldOfficeBeforeKingship Context triple: [Ramesses I, heldOfficeBeforeKingship, vizier]
-
A.
regentPreviouslyHeldOffice
Indicates that the regent held a particular office or position before assuming their regency.
-
B.
usedBeforeEnthronement
Indicates that something was in use prior to a person’s enthronement or formal assumption of a ruling position.
-
C.
predecessorAsDeFactoRuler
Indicates that one entity previously held actual ruling power over a domain or group, regardless of formal title, before another entity assumed that de facto control.
-
D.
politicalStatusBeforeReign
chosen
Indicates the political role or status an individual held prior to beginning their reign or period of rule.
-
E.
precededByAsRegent
Indicates that one entity previously served as regent before another entity, in a directly preceding position of regency.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6335dae10819096e1825741f814ed |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.