Triple
T17756431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Ramesses |
E443251
|
entity |
| Predicate | reignOfFounder |
P128233
|
FINISHED |
| Object | 1279–1213 BCE |
—
|
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: 1279–1213 BCE | Statement: [House of Ramesses, reignOfFounder, 1279–1213 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignOfFounder Context triple: [House of Ramesses, reignOfFounder, 1279–1213 BCE]
-
A.
roleInDynastyFounding
Indicates the role or contribution an entity had in the founding or establishment of a particular dynasty.
-
B.
founderOfPredecessor
Indicates that an entity is the founder of another entity that served as a predecessor to a specified organization or institution.
-
C.
realmFoundedBy
Indicates that a particular realm or domain was established or created by a specific founding entity.
-
D.
founderDynasty
Indicates that an entity is the founding member or originator of a particular dynasty.
-
E.
royalHouseFounder
Indicates that one entity is the person who founded or established the royal house or dynasty to which the other entity belongs.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841f29f08190b1a1e9624d88120f |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3cfab7edc8190b663282d565a0389 |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:10 a.m.