Triple
T9766975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chimalhuacán |
E237017
|
entity |
| Predicate | hasFoundingCulture |
P27600
|
FINISHED |
| Object | pre-Hispanic |
—
|
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: pre-Hispanic | Statement: [Chimalhuacán, hasFoundingCulture, pre-Hispanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoundingCulture Context triple: [Chimalhuacán, hasFoundingCulture, pre-Hispanic]
-
A.
hasCivilization
Indicates that an entity possesses, hosts, or is associated with an organized society or culture characterized by social, political, and technological development.
-
B.
hasCulturalLegacyIn
Indicates that an entity has left a lasting cultural influence, impact, or heritage within a particular place, community, or cultural context.
-
C.
hasDynastyFounded
Indicates that an entity is the founder or originator of a particular dynasty.
-
D.
hasAssociatedCulture
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
E.
hasArchaeologicalCulture
chosen
Indicates that an entity is associated with, belongs to, or is characterized by a particular archaeological culture.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a15e408190909745cb1c30937d |
completed | April 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.