Triple
T328516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crescent Meadow |
E6572
|
entity |
| Predicate | ecosystemService |
P8224
|
FINISHED |
| Object | 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: wildlife habitat | Statement: [Crescent Meadow, ecosystemService, wildlife habitat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ecosystemService Context triple: [Crescent Meadow, ecosystemService, wildlife habitat]
-
A.
hasEcosystemService
chosen
Indicates that one entity provides, supports, or is associated with an ecosystem service that benefits another entity or the environment.
-
B.
ecoregion
Indicates that one entity is located within, associated with, or belongs to the same ecological region as another entity.
-
C.
primaryEcosystem
Indicates the main type of ecosystem in which an entity predominantly exists or operates.
-
D.
ecoregionsInclude
Indicates that one ecoregion spatially contains or encompasses another ecoregion or area within its boundaries.
-
E.
hasBiosphere
Indicates that an entity possesses or supports a biosphere, i.e., a region where living organisms and ecological processes exist.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eaad37b0819085beda2a491da9a8 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94aab1c8190b8654708c87eeb91 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.