Triple
T924669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuitláhuac |
E19956
|
entity |
| Predicate | roleDuringConquest |
P22409
|
FINISHED |
| Object | leader of Mexica resistance |
—
|
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: leader of Mexica resistance | Statement: [Cuitláhuac, roleDuringConquest, leader of Mexica resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleDuringConquest Context triple: [Cuitláhuac, roleDuringConquest, leader of Mexica resistance]
-
A.
conqueredFrom
Indicates that one entity gained control of another entity by taking it from a third party that previously held it.
-
B.
conqueredCity
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
-
C.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
D.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
E.
allianceRole
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2970a4c8190b22cb2fd4706f62b |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b385176081909e3e8c3f647c1fd4 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.