Triple
T14771210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armenian passports |
E347135
|
entity |
| Predicate | holderRights |
P5532
|
FINISHED |
| Object | right to consular protection by Armenia abroad |
—
|
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: right to consular protection by Armenia abroad | Statement: [Armenian passports, holderRights, right to consular protection by Armenia abroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderRights Context triple: [Armenian passports, holderRights, right to consular protection by Armenia abroad]
-
A.
rightsInclude
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
-
B.
rightsManagement
Indicates the management, control, and enforcement of usage rights or permissions associated with an entity or resource.
-
C.
rights
chosen
Indicates that an entity possesses entitlements, permissions, or legal/moral claims in relation to another entity or context.
-
D.
rightsCategory
Indicates the classification or type of rights associated with an entity or relationship.
-
E.
rightsSociety
Indicates that an entity holds legal, moral, or social rights in relation to a society or collective group.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81334e08190a77d760e507d00ed |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.