Triple
T26159310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saussurea |
E660060
|
entity |
| Predicate | hasNotableRegionOfDiversity |
P12301
|
FINISHED |
| Object | Himalayas |
—
|
NE NERFINISHED |
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: Himalayas | Statement: [Saussurea, hasNotableRegionOfDiversity, Himalayas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRegionOfDiversity Context triple: [Saussurea, hasNotableRegionOfDiversity, Himalayas]
-
A.
hadPopulationDiversity
Indicates that an entity possessed a population characterized by a variety of distinct demographic or group attributes (such as ethnicity, culture, or other differentiating factors).
-
B.
notableDiversityRegion
Indicates that a region is recognized for having significant diversity, such as in its population, culture, or environment.
-
C.
hasInternalDiversity
Indicates that an entity contains multiple distinct types, elements, or subgroups within itself, rather than being uniform or homogeneous.
-
D.
centerOfDiversity
chosen
Indicates the location where a particular group, trait, or phenomenon exhibits its greatest variety or concentration of diversity.
-
E.
hadLanguageDiversity
Indicates that an entity exhibited a range of different languages used or represented within 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 26, 2026, 8:29 p.m.