Triple
T27524032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan–South Korea |
E694786
|
entity |
| Predicate | hasDiplomaticRelationSince |
P78848
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [Japan–South Korea, hasDiplomaticRelationSince, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiplomaticRelationSince Context triple: [Japan–South Korea, hasDiplomaticRelationSince, 1965]
-
A.
diplomaticRelationBetween
Indicates the existence of a formal diplomatic relationship or ties between two political entities or states.
-
B.
diplomaticRelation
Indicates a formal relationship of negotiation, communication, or representation between political entities, typically states or governments.
-
C.
hasDiplomaticRelationShiftedFrom
Indicates that the nature or status of a diplomatic relationship has changed from a previously existing form or state.
-
D.
formalDiplomaticRelationsEstablished
chosen
Indicates that official diplomatic ties have been formally initiated and recognized between two political entities.
-
E.
hasDiplomaticAction
Indicates that one entity performs, initiates, or is involved in a formal diplomatic action or engagement directed toward another entity.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 27, 2026, 1:22 p.m.