Triple
T29424056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumsey Meadow |
E746236
|
entity |
| Predicate | hasWildlifeValue |
P107152
|
FINISHED |
| Object | important wildlife habitat |
—
|
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: important wildlife habitat | Statement: [Dumsey Meadow, hasWildlifeValue, important wildlife habitat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildlifeValue Context triple: [Dumsey Meadow, hasWildlifeValue, important wildlife habitat]
-
A.
hasWildlifeHabitats
Indicates that an entity contains or supports natural environments where wildlife species live, feed, or reproduce.
-
B.
hasWildlifeSite
Indicates that a location or entity possesses, contains, or is designated as a wildlife site.
-
C.
hasWildlifeFocus
Indicates that something is primarily concerned with, dedicated to, or centered around wildlife.
-
D.
hasWildlifeStatus
Indicates the conservation or protection status assigned to wildlife associated with an entity.
-
E.
hasWildlifeUse
chosen
Indicates that something is used by or provides a functional role for wildlife, such as habitat, food, shelter, or other ecological benefits.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 3:07 p.m.