Triple
T26282223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thinite kings of early dynastic Egypt |
E661028
|
entity |
| Predicate | dynasticRange |
P142170
|
FINISHED |
| Object | Second Dynasty |
—
|
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: Second Dynasty | Statement: [Thinite kings of early dynastic Egypt, dynasticRange, Second Dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticRange Context triple: [Thinite kings of early dynastic Egypt, dynasticRange, Second Dynasty]
-
A.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
B.
dynasticScope
chosen
Indicates the range or extent of influence, authority, or relevance associated with a particular dynasty or dynastic period.
-
C.
dynasticEraName
Indicates the named historical period or era associated with a particular dynasty’s rule.
-
D.
dynastyRuled
Indicates that a particular dynasty held ruling authority or governance over a specified region, state, or people during a certain period.
-
E.
dynasticOrder
Indicates the hierarchical sequence of rulers or family lines within a dynasty, specifying who precedes or follows whom in dynastic succession.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 10:01 p.m.