Triple
T29009184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Artsakh |
E736515
|
entity |
| Predicate | announcedDissolutionEffectiveOn |
P62226
|
FINISHED |
| Object | 1 January 2024 |
—
|
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: 1 January 2024 | Statement: [Government of Artsakh, announcedDissolutionEffectiveOn, 1 January 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedDissolutionEffectiveOn Context triple: [Government of Artsakh, announcedDissolutionEffectiveOn, 1 January 2024]
-
A.
dissolutionOfParliamentDate
Indicates the date on which a parliament is formally dissolved, ending its term and legislative authority.
-
B.
lastDissolutionBefore
Indicates that one dissolution event occurred earlier in time than another specified dissolution event.
-
C.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
D.
parliamentDissolvedBy
Indicates that a parliament is formally brought to an end or terminated by a specified authority or actor.
-
E.
disbandedAt
chosen
Indicates the time or date at which an organized group, body, or entity formally ceased to exist or operate.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fda92188190b20bfd59902ed27d |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:40 a.m.