Triple
T37088212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ley de Asociaciones Religiosas y Culto Público |
E918344
|
entity |
| Predicate | tipoDeSujetoRegulado |
P68335
|
FINISHED |
| Object | iglesias |
—
|
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: iglesias | Statement: [Ley de Asociaciones Religiosas y Culto Público, tipoDeSujetoRegulado, iglesias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDeSujetoRegulado Context triple: [Ley de Asociaciones Religiosas y Culto Público, tipoDeSujetoRegulado, iglesias]
-
A.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
B.
typeOfResourceRegulated
chosen
Indicates that one entity specifies the kind or category of resource that is subject to regulation by another entity.
-
C.
typeOfAgencyRegulated
Indicates that one entity is the kind or category of agency that is subject to regulation by another entity.
-
D.
regulatorType
Indicates the specific kind or category of regulatory role or authority associated with an entity.
-
E.
subjectToRegulation
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.