Triple
T35051076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Era |
E1011330
|
entity |
| Predicate | beganWithDynasty |
P145762
|
FINISHED |
| Object | Septim 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: Septim Dynasty | Statement: [Third Era, beganWithDynasty, Septim Dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganWithDynasty Context triple: [Third Era, beganWithDynasty, Septim Dynasty]
-
A.
marksBeginningOfDynasty
chosen
Indicates that an event, person, or moment signifies the start or formal establishment of a particular dynasty.
-
B.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
C.
founderDynasty
Indicates that an entity is the founding member or originator of a particular dynasty.
-
D.
branchOfDynastyFounded
Indicates that one dynasty is a branch or offshoot of another, earlier-founded dynasty.
-
E.
hasDynastyFounded
Indicates that an entity is the founder or originator of a particular dynasty.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.