Triple
T37902728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albania–Soviet Union relations |
E945459
|
entity |
| Predicate | deteriorationBegan |
P32954
|
FINISHED |
| Object | mid‑1950s |
—
|
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: mid‑1950s | Statement: [Albania–Soviet Union relations, deteriorationBegan, mid‑1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deteriorationBegan Context triple: [Albania–Soviet Union relations, deteriorationBegan, mid‑1950s]
-
A.
reasonForFurtherDeterioration
Indicates that one condition, event, or factor is identified as the cause of additional worsening or decline in another condition or situation.
-
B.
declineBeganUnder
Indicates that a period of decline started during the tenure, rule, or administration of a specified entity.
-
C.
declineBeganInPeriod
chosen
Indicates that the onset of a decline in the subject occurred during the specified time period.
-
D.
wasDeterioratedBeforeReconstruction
Indicates that something was in a deteriorated or degraded condition prior to undergoing reconstruction.
-
E.
began
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.