Triple
T31144205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sexta Ley Constitucional |
E793874
|
entity |
| Predicate | tipo de norma |
P2826
|
FINISHED |
| Object | ley fundamental |
—
|
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: ley fundamental | Statement: [Sexta Ley Constitucional, tipo de norma, ley fundamental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipo de norma Context triple: [Sexta Ley Constitucional, tipo de norma, ley fundamental]
-
A.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
B.
normType
chosen
Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
-
C.
natureOfRule
Indicates the fundamental type or character of a rule, specifying what kind of rule it is or how it functions within a system.
-
D.
legalStandardType
Indicates the specific type or category of legal standard that governs or applies to a given legal rule, decision, or evaluation.
-
E.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:06 p.m.