Triple
T25367171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arewelian Hayeren |
E632830
|
entity |
| Predicate | hasPrimaryUsageDomain |
P70082
|
FINISHED |
| Object | education in Armenia |
—
|
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: education in Armenia | Statement: [Arewelian Hayeren, hasPrimaryUsageDomain, education in Armenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryUsageDomain Context triple: [Arewelian Hayeren, hasPrimaryUsageDomain, education in Armenia]
-
A.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
B.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
C.
hasDominantUse
chosen
Indicates that one use or function of an entity is primary or prevailing over its other possible uses.
-
D.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
E.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 21, 2026, 1:37 p.m.