Triple
T29009104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of the Republic of Artsakh |
E736514
|
entity |
| Predicate | legalStatusOfState |
P34336
|
FINISHED |
| Object | self-proclaimed |
—
|
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: self-proclaimed | Statement: [Constitution of the Republic of Artsakh, legalStatusOfState, self-proclaimed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOfState Context triple: [Constitution of the Republic of Artsakh, legalStatusOfState, self-proclaimed]
-
A.
stateAdoption
Indicates that a state formally accepts, enacts, or takes on a policy, law, standard, or practice.
-
B.
statehoodStatus
chosen
Indicates the legal or political condition of an entity regarding whether, how, or to what extent it is recognized or functions as a state.
-
C.
stateClassification
Indicates how something is categorized or classified within a particular state or status.
-
D.
statusInUnitedStates
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
-
E.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated 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_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 28, 2026, 9:40 a.m.