Triple
T35766944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sewadjkare LIV |
E1034041
|
entity |
| Predicate | hasAttestationType |
P22964
|
FINISHED |
| Object | king lists (probable) |
—
|
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: king lists (probable) | Statement: [Sewadjkare LIV, hasAttestationType, king lists (probable)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttestationType Context triple: [Sewadjkare LIV, hasAttestationType, king lists (probable)]
-
A.
hasAttestation
chosen
Indicates that there exists a formal confirmation, evidence, or certification supporting the validity or authenticity of something.
-
B.
hasLimitedAttestation
Indicates that the relationship or fact is supported by only a small number of sources, occurrences, or pieces of evidence.
-
C.
hasTypeCertificateFor
Indicates that an entity possesses a specific type of certificate that is issued for or applicable to another entity or subject.
-
D.
hasClaimType
Indicates that an entity is associated with or categorized under a specific type of claim.
-
E.
hasWitnessType
Indicates that an event, incident, or situation is associated with a specific category or type of witness involved.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.