Triple
T2794204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepi I Meryre |
E52997
|
entity |
| Predicate | reignApproximate |
P22408
|
FINISHED |
| Object | c. 2332–2283 BCE |
—
|
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: c. 2332–2283 BCE | Statement: [Pepi I Meryre, reignApproximate, c. 2332–2283 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignApproximate Context triple: [Pepi I Meryre, reignApproximate, c. 2332–2283 BCE]
-
A.
reignDuration
chosen
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
B.
correspondsToReignOf
Indicates that something (such as a time period, event, or record) matches or is associated with the duration of a specific ruler’s reign.
-
C.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
D.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
-
E.
describesReignOf
Indicates that something (such as a text, record, or account) provides information about the period during which a particular ruler or authority was in power.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddd48bcc819083f4ec59d66f0ece |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.