Triple
T3583604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himno Nacional de la República de Colombia |
E75856
|
entity |
| Predicate | regulatesPerformance |
P20527
|
FINISHED |
| Object | Colombian law |
—
|
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: Colombian law | Statement: [Himno Nacional de la República de Colombia, regulatesPerformance, Colombian law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesPerformance Context triple: [Himno Nacional de la República de Colombia, regulatesPerformance, Colombian law]
-
A.
performanceTuningBy
Indicates that an entity’s performance has been adjusted, optimized, or fine-tuned by another entity.
-
B.
impactOnPerformance
chosen
Indicates that one entity has an effect, influence, or consequence on the performance level or effectiveness of another entity.
-
C.
regulatesIn
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
-
D.
regulatesProgram
Indicates that one entity exercises control or governance over the operation, rules, or functioning of a program.
-
E.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc104846c81908b6fbde7061464b4 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.