Triple
T19008507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardigan–Sunapee region conservation lands |
E465154
|
entity |
| Predicate | hasPrimaryEcosystemType |
P964
|
FINISHED |
| Object | 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: forest | Statement: [Cardigan–Sunapee region conservation lands, hasPrimaryEcosystemType, forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryEcosystemType Context triple: [Cardigan–Sunapee region conservation lands, hasPrimaryEcosystemType, forest]
-
A.
primaryEcosystem
chosen
Indicates the main type of ecosystem in which an entity predominantly exists or operates.
-
B.
containsEcologicalTypes
Indicates that one entity includes or encompasses specific ecological types or categories within it.
-
C.
hasEcosystemService
Indicates that one entity provides, supports, or is associated with an ecosystem service that benefits another entity or the environment.
-
D.
hasEcology
Indicates that an entity has a particular ecological context, such as its habitat, environmental role, or interactions within an ecosystem.
-
E.
containsEcosystem
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a623c481908d22c9bfad9e2939 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.