Triple
T27985170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diplomatic Corps in London |
E706724
|
entity |
| Predicate | diplomaticRankIncludes |
P3078
|
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: [Diplomatic Corps in London, diplomaticRankIncludes, ambassador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diplomaticRankIncludes Context triple: [Diplomatic Corps in London, diplomaticRankIncludes, ambassador]
-
A.
diplomaticRankRelative
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.
hasDiplomaticLevel
Indicates the degree or status of formal diplomatic relations that exists between two entities.
-
D.
hasDiplomaticForm
Indicates that an entity maintains a specific type or mode of diplomatic representation or relations.
-
E.
typeOfDiplomaticRole
chosen
Indicates the specific kind or category of diplomatic position or function that an entity holds in relation to another.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 7:47 p.m.