Triple
T10317715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pueblo Mágico |
E242061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mexican government program |
C357
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Mexican government program Context triple: [Pueblo Mágico, instanceOf, Mexican government program]
-
A.
Mexican political plan
A Mexican political plan is a formal, often revolutionary, document that outlines a political movement’s principles, goals, and strategies for restructuring or challenging the existing government in Mexico.
-
B.
Mexican federal government agency
A Mexican federal government agency is an official public institution established by the federal government of Mexico to implement national policies, administer public programs, and regulate specific sectors or functions across the country.
-
C.
Mexican organization
A Mexican organization is a structured group or entity based in Mexico that coordinates people and resources to pursue specific social, economic, cultural, or political objectives within the country or in relation to it.
-
D.
federal government program
chosen
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
-
E.
United States government program
A United States government program is an organized set of activities, services, or regulations funded and administered by federal agencies to achieve specific public policy goals or address national needs.
- F. None of above.
Provenance (1 batch)
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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:49 a.m.