Triple
T25025821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec culture |
E626705
|
entity |
| Predicate | memberPolity |
P139424
|
FINISHED |
| Object | Tlacopan |
—
|
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: Tlacopan | Statement: [Aztec culture, memberPolity, Tlacopan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberPolity Context triple: [Aztec culture, memberPolity, Tlacopan]
-
A.
memberPolities
chosen
Indicates that one polity is a constituent or member entity within a larger political grouping, organization, or union.
-
B.
memberOfPoliticalInstitution
Indicates that an entity belongs to, serves in, or holds membership within a specific political body or institution.
-
C.
courtMembership
Indicates that an entity holds or has held a position as a member of a particular court or judicial body.
-
D.
isInPolity
Indicates that one entity is located within, belongs to, or falls under the jurisdiction of a particular political unit or governing authority.
-
E.
memberOfPoliticalContext
Indicates that an entity participates in, is associated with, or belongs to a particular political environment, framework, or situation.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 18, 2026, 6:07 a.m.