Triple
T37942435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayer |
E946522
|
entity |
| Predicate | usedAsEthnonymFor |
P179718
|
FINISHED |
| Object | ethnic Armenians worldwide |
—
|
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: ethnic Armenians worldwide | Statement: [Hayer, usedAsEthnonymFor, ethnic Armenians worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsEthnonymFor Context triple: [Hayer, usedAsEthnonymFor, ethnic Armenians worldwide]
-
A.
usedAsEthnicLabelIn
Indicates that something is employed as a term or label to identify or refer to an ethnic group in a particular context.
-
B.
isEthnonymFor
chosen
Indicates that one term is the ethnonym (name of a people or ethnic group) used to refer to another entity.
-
C.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
-
D.
equivalentEthnonym
Indicates that two different ethnonyms refer to the same ethnic group or people.
-
E.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:20 p.m.