Triple
T29539033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harem Conspiracy against Ramesses III |
E749435
|
entity |
| Predicate | legalProceedingOf |
P3010
|
FINISHED |
| Object | Ramesses III |
—
|
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: Ramesses III | Statement: [Harem Conspiracy against Ramesses III, legalProceedingOf, Ramesses III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalProceedingOf Context triple: [Harem Conspiracy against Ramesses III, legalProceedingOf, Ramesses III]
-
A.
legalProcedureUsed
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
B.
hasLegalProceeding
chosen
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
-
C.
legalStatusOfProceedings
Indicates the current legal standing or condition of a set of legal proceedings within a judicial or administrative process.
-
D.
requiredCourtProceeding
Indicates that a specific legal action or case must undergo a designated court proceeding or hearing.
-
E.
typeOfProceedings
Indicates the specific category or kind of legal or formal process under which an action or case is being conducted.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 28, 2026, 5 p.m.