Triple
T9615390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reglamento de la Ley de Migración |
E232205
|
entity |
| Predicate | tieneÁmbitoMaterial |
P39719
|
FINISHED |
| Object | migración |
—
|
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: migración | Statement: [Reglamento de la Ley de Migración, tieneÁmbitoMaterial, migración]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieneÁmbitoMaterial Context triple: [Reglamento de la Ley de Migración, tieneÁmbitoMaterial, migración]
-
A.
hasMaterialAspect
Indicates that something possesses a physical or tangible component or aspect as part of its overall nature or existence.
-
B.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
C.
associatedWithMaterial
Indicates a relationship where something is linked or connected to a particular material, typically as its substance, component, or relevant physical medium.
-
D.
thematicMaterial
chosen
Indicates that one entity serves as the primary recurring idea, motif, or thematic content that is developed or referenced by another entity.
-
E.
collectsMaterialType
Indicates that an entity gathers or acquires materials of a specified type.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9aabb6b88190b53547db885e0129 |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.