Triple
T10223429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deccan thorn scrub forests |
E242638
|
entity |
| Predicate | floraAdaptation |
P44707
|
FINISHED |
| Object | xerophytic |
—
|
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: xerophytic | Statement: [Deccan thorn scrub forests, floraAdaptation, xerophytic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floraAdaptation Context triple: [Deccan thorn scrub forests, floraAdaptation, xerophytic]
-
A.
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.
-
B.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
C.
adaptationIn
Indicates that something appears, is represented, or takes place within a particular adaptation of an original work.
-
D.
regionOfAdaptation
Indicates the geographic or environmental region to which an entity is specifically adapted.
-
E.
nativeToClimate
chosen
Indicates that an entity naturally originates from or is originally adapted to a specified climate or climatic 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa8305e481908ee1fc1d9eda6fa0 |
completed | April 6, 2026, 12:43 p.m. |
| PD | Predicate disambiguation | batch_69d3955f61f88190b8d37ff645cd44d3 |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:10 a.m.