Triple
T20313745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Nature Reserves in Wales |
E510324
|
entity |
| Predicate | typicalHabitats |
P22357
|
FINISHED |
| Object | upland heath |
—
|
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: upland heath | Statement: [National Nature Reserves in Wales, typicalHabitats, upland heath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHabitats Context triple: [National Nature Reserves in Wales, typicalHabitats, upland heath]
-
A.
featuresHabitat
chosen
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
B.
typicalHabitatInHost
Indicates that an organism’s usual or characteristic habitat occurs within a particular host organism.
-
C.
typicalVegetationAdaptation
Indicates the characteristic ways in which vegetation is adapted to the prevailing environmental conditions of a given area.
-
D.
preferredHabitat
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
-
E.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67745e2448190b5611382fe338bb2 |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.