Triple
T342890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US–UK Bilateral Working Groups |
E6874
|
entity |
| Predicate | relationshipManaged |
P12071
|
FINISHED |
| Object | US–UK diplomatic relationship |
—
|
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: US–UK diplomatic relationship | Statement: [US–UK Bilateral Working Groups, relationshipManaged, US–UK diplomatic relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipManaged Context triple: [US–UK Bilateral Working Groups, relationshipManaged, US–UK diplomatic relationship]
-
A.
associatedWithManager
Indicates that an entity has a managerial connection or relationship with a specific manager.
-
B.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
C.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
D.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
E.
spouseOrLover
Indicates a romantic partnership between two entities, whether formalized as a spouse or existing as a lover.
- F. None of above. chosen
Provenance (4 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eafef8c88190a5932eb2c6ac4a5d |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e9530c98819085025efe4e04aa7e |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0a4c448190a8a179daa9b90645 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.