Triple
T25830557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Ashe |
E650649
|
entity |
| Predicate | diplomaticPositionToCountry |
P2921
|
FINISHED |
| Object | Poland |
—
|
NE NERFINISHED |
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: Poland | Statement: [Victor Ashe, diplomaticPositionToCountry, Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diplomaticPositionToCountry Context triple: [Victor Ashe, diplomaticPositionToCountry, Poland]
-
A.
diplomaticRegion
Indicates the geographic or political area within which a diplomatic role, mission, or activity is formally recognized or exercised.
-
B.
countryOfDiplomaticMission
Indicates that a diplomatic mission is located in and officially accredited to a particular country.
-
C.
diplomaticRankRelative
Indicates the relative seniority or hierarchical ranking between two diplomatic positions or titles.
-
D.
diplomaticRelation
Indicates a formal relationship of negotiation, communication, or representation between political entities, typically states or governments.
-
E.
diplomaticRole
chosen
Indicates that an entity holds or has held an official diplomatic position or function in relation to another entity or context.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 7:38 a.m.