Triple
T27169355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iuput I |
E682861
|
entity |
| Predicate | coexistence |
P12845
|
FINISHED |
| Object | coexisted with other contemporary dynasties in Egypt |
—
|
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: coexisted with other contemporary dynasties in Egypt | Statement: [Iuput I, coexistence, coexisted with other contemporary dynasties in Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coexistence Context triple: [Iuput I, coexistence, coexisted with other contemporary dynasties in Egypt]
-
A.
canCoexistWith
Indicates that two entities are able to exist together in the same context or environment without conflict, interference, or mutual exclusion.
-
B.
cooperationAmong
Indicates a relationship in which multiple entities work together collaboratively toward shared goals or mutual benefit.
-
C.
cooperationAgainst
Indicates a collaborative relationship in which two or more entities work together in opposition to a shared target or adversary.
-
D.
cooperateThrough
Indicates that entities work together or coordinate their actions by means of a specific intermediary, method, or channel.
-
E.
coexistedWith
chosen
Indicates that two entities existed at the same time and in the same context or environment, without implying any specific type of interaction between them.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62545e210819090004d7c65f4898d |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:22 a.m.