Triple
T31310992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papyrus Anastasi I |
E798461
|
entity |
| Predicate | approximateDynasty |
P179535
|
FINISHED |
| Object | 19th Dynasty of Egypt |
—
|
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: 19th Dynasty of Egypt | Statement: [Papyrus Anastasi I, approximateDynasty, 19th Dynasty of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDynasty Context triple: [Papyrus Anastasi I, approximateDynasty, 19th Dynasty of Egypt]
-
A.
possibleDynasty
chosen
Indicates that one entity could plausibly be the ruling dynasty associated with, or historically linked to, another entity.
-
B.
builtDynastyAround
Indicates establishing and sustaining a long-term, dominant success or legacy centered on a particular person, group, or core element.
-
C.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
-
D.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
-
E.
dynastyAlsoKnownAs
Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 29, 2026, 9:15 p.m.