Triple
T1102803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narmer |
E25418
|
entity |
| Predicate | reignPeriod |
P4210
|
FINISHED |
| Object | late 32nd century 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: late 32nd century BCE | Statement: [Narmer, reignPeriod, late 32nd century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignPeriod Context triple: [Narmer, reignPeriod, late 32nd century BCE]
-
A.
reignDuration
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
B.
periodOfRule
chosen
Indicates the span of time during which an entity exercised authority, control, or governance over something.
-
C.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
-
D.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
E.
adoptedDuringReignOf
Indicates that one entity (such as a law, policy, or practice) was adopted or came into effect while another entity (typically a ruler or leader) was in power or reigning.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c375848190baec4d534f489616 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b7472c848190b0643872f67084a2 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.