Triple
T16407346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Setnakhte |
E398467
|
entity |
| Predicate | disputedOrigins |
P50823
|
FINISHED |
| Object | possibly of non-royal birth |
—
|
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: possibly of non-royal birth | Statement: [Setnakhte, disputedOrigins, possibly of non-royal birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputedOrigins Context triple: [Setnakhte, disputedOrigins, possibly of non-royal birth]
-
A.
disputed
chosen
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
disputeOrigin
Indicates that there is disagreement or uncertainty about the source, cause, or initial point of something.
-
D.
debatedBetween
Indicates a situation in which two or more parties engage in a discussion or argument over differing views about a particular issue or topic.
-
E.
originatingDispute
Indicates that one entity is the source, cause, or initial context of a particular dispute involving another entity.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d36b808190b6b8c412ae0d2faa |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.