Triple
T34541049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial House of Mexico |
E886806
|
entity |
| Predicate | originCountryOfDynasty |
P129610
|
FINISHED |
| Object | Mexico |
E346
|
NE 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: Mexico | Statement: [Imperial House of Mexico, originCountryOfDynasty, Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originCountryOfDynasty Context triple: [Imperial House of Mexico, originCountryOfDynasty, Mexico]
-
A.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
B.
royalHouseOriginCountry
chosen
Indicates the country from which a royal house or dynasty originates.
-
C.
countryOfDynasticConnection
Indicates that there exists a historical dynastic link—such as through ruling families, royal marriages, or shared dynasties—between the subject and the referenced country.
-
D.
foundingDynastyOf
Indicates that a particular dynasty is the original founding ruling house or lineage of a specified political entity, state, or realm.
-
E.
regionOfDynasty
Indicates the geographic region or area in which a given dynasty held power or was primarily based.
- F. None of above.
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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729c656ac8190a31bc4528985ccaf |
completed | June 21, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.