Triple
T25860808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Napata and Memphis |
E651471
|
entity |
| Predicate | associatedWithRulers |
P194735
|
FINISHED |
| Object | Piye |
—
|
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: Piye | Statement: [Napata and Memphis, associatedWithRulers, Piye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRulers Context triple: [Napata and Memphis, associatedWithRulers, Piye]
-
A.
associatedWithMonarch
Indicates a relationship where an entity has a connection or affiliation with a monarch, such as through service, governance, lineage, or formal association.
-
B.
associatedWithRulerOrMinister
chosen
Indicates a relationship in which an entity is connected or linked to a ruler or minister, such as through service, affiliation, or influence.
-
C.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
D.
associatedDynastyRuler
Indicates a relationship where a dynasty is linked to the ruler who governed or is historically connected with it.
-
E.
associatedWithMonarchy
Indicates a relationship in which something has a connection, link, or relevance to a monarchy or monarchical system.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 22, 2026, 8:05 a.m.