Triple
T18430450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smenkhkare |
E450253
|
entity |
| Predicate | coregencyDebate |
P131573
|
FINISHED |
| Object | possibly co-regent with Akhenaten |
—
|
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 co-regent with Akhenaten | Statement: [Smenkhkare, coregencyDebate, possibly co-regent with Akhenaten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coregencyDebate Context triple: [Smenkhkare, coregencyDebate, possibly co-regent with Akhenaten]
-
A.
canDebate
Indicates that one entity has the ability or permission to engage in a debate or argumentative discussion with another entity.
-
B.
debatedWithin
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
C.
majorDebateWith
Indicates a significant, often public or formal, debate or dispute occurring between two entities.
-
D.
debatedAs
Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
-
E.
fieldOfDebate
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
- F. None of above. chosen
Provenance (4 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b16b9c881908245c888a4b785bf |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:26 a.m.