Triple
T35766934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sewadjkare LIV |
E1034041
|
entity |
| Predicate | hasRegionOfRule |
P15936
|
FINISHED |
| Object | Egypt |
E1136
|
NE 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: Egypt | Statement: [Sewadjkare LIV, hasRegionOfRule, Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionOfRule Context triple: [Sewadjkare LIV, hasRegionOfRule, Egypt]
-
A.
hasRegionFunction
Indicates that a region is associated with a particular function, role, or operational purpose.
-
B.
regionRuled
chosen
Indicates that a particular region is governed or controlled by a specified ruler or authority.
-
C.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
hasRegionKey
Indicates that an entity is associated with a specific region through a unique identifying key.
- F. None of above.
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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3885fffdb481908b339b21fd35bddf |
completed | June 22, 2026, 12:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.