Triple
T12672988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ley 1185 de 2008 |
E302732
|
entity |
| Predicate | aplicación |
P106222
|
FINISHED |
| Object | todo el territorio colombiano |
—
|
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: todo el territorio colombiano | Statement: [Ley 1185 de 2008, aplicación, todo el territorio colombiano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aplicación Context triple: [Ley 1185 de 2008, aplicación, todo el territorio colombiano]
-
A.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
-
B.
componentApplication
Indicates that one entity is an application or use-case instance that is built from, configured by, or otherwise realized through another entity serving as its component.
-
C.
typeOfApplication
Indicates the specific category or kind of application involved in the relationship or action.
-
D.
commonApplication
Indicates that multiple entities share or participate in the same application, process, or usage context.
-
E.
relatedApplication
Indicates that one application has a defined connection or association with another application, such as dependency, complementarity, or functional linkage.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961af991c8190b6079cb57e593b8f |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:20 p.m.