Triple
T29009160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Artsakh |
E736515
|
entity |
| Predicate | hadJudicialPartner |
P63272
|
FINISHED |
| Object | Judiciary of Artsakh |
—
|
NE NERFINISHED |
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: Judiciary of Artsakh | Statement: [Government of Artsakh, hadJudicialPartner, Judiciary of Artsakh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadJudicialPartner Context triple: [Government of Artsakh, hadJudicialPartner, Judiciary of Artsakh]
-
A.
judicialPartner
Indicates a formal partnership or collaborative relationship between entities within a judicial or court-related context.
-
B.
hadJudicialCounterpart
chosen
Indicates that one legal or judicial entity corresponded to, or was matched by, another entity serving an equivalent judicial role or function.
-
C.
lawPartnerOf
Indicates a professional relationship in which two individuals are partners in the same law firm or legal practice.
-
D.
hadJudicialFunction
Indicates that an entity exercised or was assigned an official judicial role, authority, or responsibility in relation to another entity or context.
-
E.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with 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_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_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:40 a.m.