Triple
T8966639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morena (Mexico) |
E214151
|
entity |
| Predicate | registeredAsPoliticalPartyYear |
P7695
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Morena (Mexico), registeredAsPoliticalPartyYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registeredAsPoliticalPartyYear Context triple: [Morena (Mexico), registeredAsPoliticalPartyYear, 2014]
-
A.
registeredAsPoliticalParty
chosen
Indicates that an entity is officially recorded and recognized as a political party by the relevant authority or registry.
-
B.
namedForPoliticalParty
Indicates that an entity is named after or in honor of a specific political party.
-
C.
hasAuthorPoliticalParty
Indicates that a political party is the one to which the author of a work or document belongs or is affiliated.
-
D.
includesPoliticalPartiesFrom
Indicates that a collection, group, or context contains or encompasses one or more political parties originating from a specified source or jurisdiction.
-
E.
hasRepresentativeParty
Indicates that an entity is officially represented or acted for by a particular political party or organized group.
- 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67623818819096aee155a9b43e8f |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:01 p.m.