Triple
T4603589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia and China |
E100375
|
entity |
| Predicate | politicalDialogue |
P38190
|
FINISHED |
| Object | regular high-level summits |
—
|
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: regular high-level summits | Statement: [Russia and China, politicalDialogue, regular high-level summits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalDialogue Context triple: [Russia and China, politicalDialogue, regular high-level summits]
-
A.
hasPoliticalDialogue
chosen
Indicates that there is an exchange or interaction between entities involving political topics, issues, or negotiations.
-
B.
broadcastsDebates
Indicates that one entity transmits or airs debates for an audience, typically via a communication medium such as television, radio, or online platforms.
-
C.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
-
D.
enteredPoliticalDebateIn
Indicates that an entity took part in a political debate that occurred in a specified place or context.
-
E.
languageOfDebate
Indicates that a specified language is the one used for conducting a particular debate.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5975ec688190839bd22669343a76 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.