Triple
T28636012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Spain frontier regions |
E724786
|
entity |
| Predicate | alliedGroupUsedByAuthorities |
P49282
|
FINISHED |
| Object | Tlaxcalans |
—
|
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: Tlaxcalans | Statement: [New Spain frontier regions, alliedGroupUsedByAuthorities, Tlaxcalans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedGroupUsedByAuthorities Context triple: [New Spain frontier regions, alliedGroupUsedByAuthorities, Tlaxcalans]
-
A.
alliedGroups
Indicates that two or more groups are formally cooperating or aligned in support of shared goals or interests.
-
B.
alliedAgency
Indicates that one agency has a formal alliance or cooperative partnership relationship with another agency.
-
C.
alliedUser
Indicates that one user is associated with or aligned as an ally to another user, typically implying cooperation or shared interests.
-
D.
alliedDesignation
chosen
Indicates that one entity assigns or recognizes an allied status or designation for another entity.
-
E.
alliedUsers
Indicates that two users are in an alliance or cooperative relationship with each other.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:40 a.m.