Triple
T15458163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colombian embassies and consulates |
E371826
|
entity |
| Predicate | typicalHeadOfConsulate |
P2921
|
FINISHED |
| Object | consul |
—
|
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: consul | Statement: [Colombian embassies and consulates, typicalHeadOfConsulate, consul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHeadOfConsulate Context triple: [Colombian embassies and consulates, typicalHeadOfConsulate, consul]
-
A.
overseesConsulatesOf
Indicates that one entity has authority over, manages, or supervises the consulates belonging to another entity.
-
B.
haveConsulates
Indicates that one country maintains consular offices or consulates within the territory of another country.
-
C.
hasConsulateOfUnitedStatesIn
Indicates that a consulate of the United States is located in the specified place.
-
D.
diplomaticRole
chosen
Indicates that an entity holds or has held an official diplomatic position or function in relation to another entity or context.
-
E.
hasConsularSection
Indicates that an entity (typically a diplomatic mission or embassy) includes or is associated with a consular section responsible for consular services.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f1623f0819086f6fc2bfd536609 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:32 a.m.