Triple
T30606228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | פּוֹטִיפַר |
E779051
|
entity |
| Predicate | servesRuler |
P8405
|
FINISHED |
| Object | Pharaoh |
—
|
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: Pharaoh | Statement: [פּוֹטִיפַר, servesRuler, Pharaoh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRuler Context triple: [פּוֹטִיפַר, servesRuler, Pharaoh]
-
A.
providedRulerFor
Indicates that one entity supplied or designated another entity to serve as the ruler or governing authority over a particular domain or group.
-
B.
involvesRuler
chosen
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
C.
usedByRuler
Indicates that something is employed, utilized, or otherwise put to use by a ruler or governing authority.
-
D.
recognizedAsRuler
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
-
E.
currentRuler
Indicates that one entity is the present reigning ruler or head of state of another entity (such as a country, region, or polity).
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: April 29, 2026, 8:25 p.m.