Triple
T29380117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ugandan high commissions |
E745111
|
entity |
| Predicate | diplomaticRankEquivalentTo |
P126996
|
FINISHED |
| Object | embassy |
—
|
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: embassy | Statement: [Ugandan high commissions, diplomaticRankEquivalentTo, embassy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diplomaticRankEquivalentTo Context triple: [Ugandan high commissions, diplomaticRankEquivalentTo, embassy]
-
A.
diplomaticRankRelative
chosen
Indicates the relative seniority or hierarchical ranking between two diplomatic positions or titles.
-
B.
hasDiplomaticRankHead
Indicates that an entity serving as a head (e.g., of a mission or organization) holds a specific diplomatic rank.
-
C.
diplomaticStatusConferred
Indicates that a formal diplomatic status or recognition has been officially granted from one party to another.
-
D.
diplomaticRelation
Indicates a formal relationship of negotiation, communication, or representation between political entities, typically states or governments.
-
E.
hasDiplomaticLevel
Indicates the degree or status of formal diplomatic relations that exists between two entities.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 2:34 p.m.