Triple
T37902735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albania–Soviet Union relations |
E945459
|
entity |
| Predicate | formalBreak |
P40216
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Albania–Soviet Union relations, formalBreak, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalBreak Context triple: [Albania–Soviet Union relations, formalBreak, 1961]
-
A.
breakType
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
B.
breaksWith
chosen
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
C.
break
Indicates that one entity causes another entity to separate into pieces, stop functioning, or otherwise lose its normal integrity or continuity.
-
D.
formedByBreakWith
Indicates that something came into existence as a result of a split, rupture, or separation from a prior entity or group.
-
E.
breakDirection
Indicates the direction in which something breaks, splits, or fractures relative to a reference point or orientation.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:20 p.m.