Triple
T30298010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramesses XI |
E770572
|
entity |
| Predicate | kingdomPeriod |
P51877
|
FINISHED |
| Object | New Kingdom of Egypt |
—
|
NE NERFINISHED |
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: New Kingdom of Egypt | Statement: [Ramesses XI, kingdomPeriod, New Kingdom of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingdomPeriod Context triple: [Ramesses XI, kingdomPeriod, New Kingdom of Egypt]
-
A.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
B.
eraOfHistoricalKingdom
chosen
Indicates the historical time period during which a particular kingdom existed or held prominence.
-
C.
eraChronology
Indicates the temporal ordering relationship that places an era within a specific position in a broader historical or chronological sequence.
-
D.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
E.
chronologicalPeriodApprox
Indicates that one entity is associated with a time period that is approximately, but not exactly, the same as the time period of another entity.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681386a748190b0d383b7c580ab47 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:48 p.m.