Triple
T34691904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moroccan monarchy |
E890920
|
entity |
| Predicate | continuousDynasticRuleSince |
P89398
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Moroccan monarchy, continuousDynasticRuleSince, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuousDynasticRuleSince Context triple: [Moroccan monarchy, continuousDynasticRuleSince, 17th century]
-
A.
dynasticInheritance
Indicates that rights, titles, or property are passed down through a family line according to established rules of succession.
-
B.
successorDynastyContinuity
chosen
Indicates that one dynasty directly continues or succeeds another in a continuous line of rule or authority.
-
C.
dynasticPrinciple
Indicates that a relationship is governed by rules of hereditary succession or dynastic inheritance within a ruling family or lineage.
-
D.
dynasticLegacy
Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
-
E.
dynasticSequence
Indicates that one dynasty or ruling line follows another in a historically ordered 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 1, 2026, 2:05 a.m.