Triple
T502767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential Palace of Colombia |
E10434
|
entity |
| Predicate | principalWorkplaceOf |
P1527
|
FINISHED |
| Object | President of Colombia |
—
|
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: President of Colombia | Statement: [Presidential Palace of Colombia, principalWorkplaceOf, President of Colombia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalWorkplaceOf Context triple: [Presidential Palace of Colombia, principalWorkplaceOf, President of Colombia]
-
A.
locationOfWork
chosen
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
B.
formerEmployer
Indicates that one entity previously employed the other but no longer does so.
-
C.
positionInWork
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
D.
residentCompany
Indicates that a company is based in, operates from, or has its primary residence in a particular location or jurisdiction.
-
E.
basisOfOffice
Indicates the foundational principle, authority, or justification upon which an office or official position is established or exercised.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1339748819089f89691a1698dd9 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.