Triple
T34541024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial House of Mexico |
E886806
|
entity |
| Predicate | hasImperialPeriod |
P183541
|
FINISHED |
| Object | First Mexican Empire |
—
|
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: First Mexican Empire | Statement: [Imperial House of Mexico, hasImperialPeriod, First Mexican Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImperialPeriod Context triple: [Imperial House of Mexico, hasImperialPeriod, First Mexican Empire]
-
A.
imperialPeriodEnd
Indicates the point in time or event at which an imperial period or era comes to an end.
-
B.
functionDuringImperialEra
Indicates that a function, role, or activity occurred or was in effect during the imperial era.
-
C.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
-
D.
originatedInReignOf
Indicates that something began, was initiated, or first came into existence during the rule or governing period of a particular ruler or authority.
-
E.
hasHistoricalEmpire
Indicates that an entity once possessed, controlled, or was associated with a significant imperial power in the past.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 1, 2026, 2:02 a.m.