Triple
T25001196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986 Goodwill Games |
E625722
|
entity |
| Predicate | hasTypeOfDiplomacy |
P166107
|
FINISHED |
| Object | sports diplomacy |
—
|
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: sports diplomacy | Statement: [1986 Goodwill Games, hasTypeOfDiplomacy, sports diplomacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDiplomacy Context triple: [1986 Goodwill Games, hasTypeOfDiplomacy, sports diplomacy]
-
A.
hasDiplomaticForm
Indicates that an entity maintains a specific type or mode of diplomatic representation or relations.
-
B.
hasDiplomaticTheme
Indicates that something involves or centers on diplomatic relations, negotiations, or international political interactions.
-
C.
hasDiplomaticLevel
Indicates the degree or status of formal diplomatic relations that exists between two entities.
-
D.
diplomaticType
Indicates the specific category or nature of a diplomatic relationship or role that exists between entities.
-
E.
hasDiplomaticFormat
Indicates that a diplomatic communication, document, or interaction follows a specific recognized diplomatic format or protocol.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 18, 2026, 6:04 a.m.