Triple
T869375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Malinche |
E18774
|
entity |
| Predicate | nameUsedAs |
P13305
|
FINISHED |
| Object | term "malinchismo" in Mexican Spanish |
—
|
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: term "malinchismo" in Mexican Spanish | Statement: [La Malinche, nameUsedAs, term "malinchismo" in Mexican Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameUsedAs Context triple: [La Malinche, nameUsedAs, term "malinchismo" in Mexican Spanish]
-
A.
nameUsedIn
chosen
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
B.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
C.
nameUsedToAvoid
Indicates that one entity uses a particular name or designation in order to avoid another entity or an unwanted situation involving that entity.
-
D.
nameUsedToAccommodate
Indicates that a particular name was previously used to refer to or accommodate an entity, but is no longer its current or primary name.
-
E.
usedPseudonym
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac811e548190a72b7a10b5ea8665 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.