Triple
T17472694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter–Fryingpan Wilderness |
E425457
|
entity |
| Predicate | plantCommunity |
P953
|
FINISHED |
| Object | Engelmann spruce–subalpine fir forest |
—
|
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: Engelmann spruce–subalpine fir forest | Statement: [Hunter–Fryingpan Wilderness, plantCommunity, Engelmann spruce–subalpine fir forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantCommunity Context triple: [Hunter–Fryingpan Wilderness, plantCommunity, Engelmann spruce–subalpine fir forest]
-
A.
speciesComposition
Indicates the makeup and relative proportions of different species present within a defined group, sample, or environment.
-
B.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
C.
vegetationType
chosen
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
D.
vegetationStructure
Indicates the structural characteristics or arrangement of plant life in an area, such as its layering, density, or complexity.
-
E.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451b8a51081908d94bebe2417e3d3 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.