Triple
T33360903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipality of Santiago de Cali |
E854216
|
entity |
| Predicate | knownForGoverning |
P125527
|
FINISHED |
| Object | major Colombian city |
—
|
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: major Colombian city | Statement: [Municipality of Santiago de Cali, knownForGoverning, major Colombian city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForGoverning Context triple: [Municipality of Santiago de Cali, knownForGoverning, major Colombian city]
-
A.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
B.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
C.
governsAreaKnownFor
chosen
Indicates that a governing entity exercises authority over an area that is notably recognized for a particular characteristic, feature, or attribute.
-
D.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
E.
governsRoleOf
Indicates that one entity has authority or control over the role, responsibilities, or functions assigned to another entity.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:34 a.m.