Triple
T555042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armenia |
E11923
|
entity |
| Predicate | diasporaSignificant |
P2103
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Armenia, diasporaSignificant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diasporaSignificant Context triple: [Armenia, diasporaSignificant, true]
-
A.
hasDiaspora
chosen
Indicates that a group, community, or population has members who have dispersed or settled outside their original homeland or region.
-
B.
demographicSignificanceIn
Indicates that something has notable demographic importance, impact, or representativeness within a specified population, group, or region.
-
C.
hasSignificantPopulationGroup
Indicates that an entity contains or is associated with a notable or substantial subgroup of a population, distinguished by shared characteristics or attributes.
-
D.
centerOfDiversity
Indicates the location where a particular group, trait, or phenomenon exhibits its greatest variety or concentration of diversity.
-
E.
hasRegionalSignificance
Indicates that something holds particular importance, influence, or relevance within a specific geographic region.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991dd7008190a6c1bc8bc832456d |
completed | March 1, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.