Triple
T6099473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian floristic region |
E135957
|
entity |
| Predicate | floraAdaptedTo |
P8732
|
FINISHED |
| Object | nutrient-poor soils |
—
|
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: nutrient-poor soils | Statement: [Australian floristic region, floraAdaptedTo, nutrient-poor soils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floraAdaptedTo Context triple: [Australian floristic region, floraAdaptedTo, nutrient-poor soils]
-
A.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
B.
nativeToClimate
Indicates that an entity naturally originates from or is originally adapted to a specified climate or climatic region.
-
C.
ecotypeOf
Indicates that one entity is an ecotype, i.e., a locally adapted variant or form, of another entity within the same species.
-
D.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
E.
growsIn
chosen
Indicates that one entity develops, thrives, or increases in size or number within a specified environment, medium, or location.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3970808190ba90f5e4235db9f2 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.