Triple
T26717295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estatuto Orgánico de Cundinamarca |
E673601
|
entity |
| Predicate | seInscribeEn |
P123643
|
FINISHED |
| Object | ordenamiento jurídico 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: ordenamiento jurídico colombiano | Statement: [Estatuto Orgánico de Cundinamarca, seInscribeEn, ordenamiento jurídico colombiano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seInscribeEn Context triple: [Estatuto Orgánico de Cundinamarca, seInscribeEn, ordenamiento jurídico colombiano]
-
A.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
B.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
C.
inscriptionSupport
chosen
Indicates that one entity serves as the physical surface or material on which another entity (an inscription) is written, carved, or otherwise recorded.
-
D.
inscriptionProcess
Indicates the process or method by which an inscription is created, applied, or recorded on a surface or object.
-
E.
inscriptionForm
Indicates the physical or structural form in which an inscription is presented (e.g., carved, painted, stamped, or otherwise rendered).
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617fd82bc8190bade06f46cfcb4a3 |
completed | May 2, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:38 a.m.