Triple
T1418564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manas National Park |
E31970
|
entity |
| Predicate | containsEcosystemType |
P1888
|
FINISHED |
| Object | sub-Himalayan grassland |
—
|
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: sub-Himalayan grassland | Statement: [Manas National Park, containsEcosystemType, sub-Himalayan grassland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEcosystemType Context triple: [Manas National Park, containsEcosystemType, sub-Himalayan grassland]
-
A.
containsEcosystem
chosen
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
-
B.
hasEcosystemService
Indicates that one entity provides, supports, or is associated with an ecosystem service that benefits another entity or the environment.
-
C.
hasEcology
Indicates that an entity has a particular ecological context, such as its habitat, environmental role, or interactions within an ecosystem.
-
D.
hasEnvironmentType
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
E.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c40631e881909ddf81a2eb84af1c |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.