Triple
T34959379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ankh-Merenre |
E1008209
|
entity |
| Predicate | hasRulerDuringConstruction |
P69612
|
FINISHED |
| Object | Merenre Nemtyemsaf I |
—
|
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: Merenre Nemtyemsaf I | Statement: [Ankh-Merenre, hasRulerDuringConstruction, Merenre Nemtyemsaf I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulerDuringConstruction Context triple: [Ankh-Merenre, hasRulerDuringConstruction, Merenre Nemtyemsaf I]
-
A.
rulerDuringConstruction
chosen
Indicates that a particular person held ruling authority over a place or polity during the time a specific construction project was carried out.
-
B.
hasRulerDuringPhase
Indicates that a specified entity serves as the ruler of another entity during a particular phase or period.
-
C.
hasFirstRuler
Indicates that an entity has another entity as its earliest or original ruler.
-
D.
constructedByRuler
Indicates that something was built, commissioned, or otherwise created under the authority or direction of a specific ruler.
-
E.
hasEarlyPhaseRuler
Indicates that an entity served as a ruler during the early phase or initial period of another entity's existence or development.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.