Triple
T7010469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty-eighth Dynasty of Egypt |
E162566
|
entity |
| Predicate | nativeDynasty |
P73647
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Twenty-eighth Dynasty of Egypt, nativeDynasty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeDynasty Context triple: [Twenty-eighth Dynasty of Egypt, nativeDynasty, true]
-
A.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
-
B.
creatorDynasty
Indicates the historical dynasty or ruling period during which the creator of an entity lived or was active.
-
C.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
D.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
-
E.
reignInDynasty
Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc3917c481909a288c3e56630c48 |
completed | March 27, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c790288190b7cbbaa4a5f9c91d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8a4930081908f1ae1e6ca8a514c |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:34 p.m.