Triple
T2559221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Party of Labour of Albania |
E57202
|
entity |
| Predicate | breakWithYugoslavia |
P19550
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Party of Labour of Albania, breakWithYugoslavia, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakWithYugoslavia Context triple: [Party of Labour of Albania, breakWithYugoslavia, 1948]
-
A.
brokeTreatyWith
Indicates that one party violated the terms of a formal agreement or treaty it had with another party.
-
B.
diplomaticRelationsSeveredYear
chosen
Indicates the year in which formal diplomatic relations between the referenced parties were officially severed.
-
C.
wasDividedByTreaty
Indicates that an entity (such as a territory or region) was partitioned or separated as the result of a formal treaty or agreement.
-
D.
attemptedArmisticeWith
Indicates an effort by one party to initiate or negotiate a ceasefire or peace agreement with another party.
-
E.
concludedWar
Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.