Triple
T29361451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Council of Nagorno-Karabakh |
E744600
|
entity |
| Predicate | hadMembersSelectedBy |
P381
|
FINISHED |
| Object | elections in Nagorno-Karabakh |
—
|
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: elections in Nagorno-Karabakh | Statement: [Supreme Council of Nagorno-Karabakh, hadMembersSelectedBy, elections in Nagorno-Karabakh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMembersSelectedBy Context triple: [Supreme Council of Nagorno-Karabakh, hadMembersSelectedBy, elections in Nagorno-Karabakh]
-
A.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
B.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
C.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another entity.
-
D.
selectionMadeBy
chosen
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
E.
holderSelection
Indicates that a particular entity has been chosen or designated to serve as the holder of another entity or resource.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6698892e88190b076bb0cdf159d8b |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:18 p.m.