Triple
T30273597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morena |
E769870
|
entity |
| Predicate | hasDominantStatusIn |
P2547
|
FINISHED |
| Object | Mexican politics |
—
|
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: Mexican politics | Statement: [Morena, hasDominantStatusIn, Mexican politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominantStatusIn Context triple: [Morena, hasDominantStatusIn, Mexican politics]
-
A.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
B.
hasDomesticDominanceIn
Indicates that an entity holds a leading or dominant position within a specified domestic (home-country) market or context.
-
C.
dominantOn
chosen
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
D.
hasDominanceSystem
Indicates that one entity maintains a structured hierarchy of power or control over others within a social or organizational system.
-
E.
hasDominated
Indicates that one entity has exercised overwhelming control, superiority, or influence over another, often in a sustained or decisive manner.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 7:44 p.m.