Triple
T31431977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irano-Turanian region |
E801819
|
entity |
| Predicate | hasFloristicEndemismLevel |
P8223
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Irano-Turanian region, hasFloristicEndemismLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloristicEndemismLevel Context triple: [Irano-Turanian region, hasFloristicEndemismLevel, high]
-
A.
hasEndemismLevel
chosen
Indicates the degree to which something is restricted or native to a particular geographic area or region.
-
B.
hasFloristicRegion
Indicates that an entity is located in, associated with, or belongs to a particular floristic (plant-distribution) region.
-
C.
hasFloristicSubregion
Indicates that a region is part of, or contained within, a more specific floristic subregion in terms of its plant composition or flora classification.
-
D.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
E.
hasEndemicSubspecies
Indicates that a species has one or more subspecies that are native and restricted to a particular geographic area.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 30, 2026, 8:58 p.m.