Triple
T27297834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukurthi National Park |
E688816
|
entity |
| Predicate | endemicFlora |
P954
|
FINISHED |
| Object | shola tree species |
—
|
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: shola tree species | Statement: [Mukurthi National Park, endemicFlora, shola tree species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endemicFlora Context triple: [Mukurthi National Park, endemicFlora, shola tree species]
-
A.
studiedFloraOf
Indicates that a subject conducted research or examination on the plant life (flora) of a specified object or region.
-
B.
hasEndemicSpecies
chosen
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
C.
associatedFlora
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
-
D.
hasFloristicRegion
Indicates that an entity is located in, associated with, or belongs to a particular floristic (plant-distribution) region.
-
E.
hasEndemismLevel
Indicates the degree to which something is restricted or native to a particular geographic area or 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62781a37c8190aa99f316b45ef952 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:20 a.m.