Triple
T32272637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican federal system |
E824454
|
entity |
| Predicate | stateAutonomyIn |
P195240
|
FINISHED |
| Object | local legislation |
—
|
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: local legislation | Statement: [Mexican federal system, stateAutonomyIn, local legislation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateAutonomyIn Context triple: [Mexican federal system, stateAutonomyIn, local legislation]
-
A.
stateFederation
Indicates that a state is a member of, or participates in, a larger federal union or federation.
-
B.
states
Indicates that an entity formally declares, expresses, or asserts a fact, opinion, or condition about another entity or situation.
-
C.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
D.
statehoodStatus
Indicates the legal or political condition of an entity regarding whether, how, or to what extent it is recognized or functions as a state.
-
E.
traditionalStateOrTerritory
Indicates that an entity is located within, associated with, or belongs to a traditional state or territory as defined by historical or customary boundaries.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: May 1, 2026, 12:42 a.m.