Triple
T36822722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Lankan diplomatic missions |
E909928
|
entity |
| Predicate | diplomaticRankOfHeads |
P13277
|
FINISHED |
| Object | ambassador |
—
|
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: ambassador | Statement: [Sri Lankan diplomatic missions, diplomaticRankOfHeads, ambassador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diplomaticRankOfHeads Context triple: [Sri Lankan diplomatic missions, diplomaticRankOfHeads, ambassador]
-
A.
hasDiplomaticRankHead
chosen
Indicates that an entity serving as a head (e.g., of a mission or organization) holds a specific diplomatic rank.
-
B.
diplomaticRankRelative
Indicates the relative seniority or hierarchical ranking between two diplomatic positions or titles.
-
C.
diplomaticRole
Indicates that an entity holds or has held an official diplomatic position or function in relation to another entity or context.
-
D.
diplomaticRelation
Indicates a formal relationship of negotiation, communication, or representation between political entities, typically states or governments.
-
E.
diplomaticConnections
Indicates the existence of formal or informal diplomatic relationships or channels of communication 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.