Triple
T5234755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Tree |
E118194
|
entity |
| Predicate | foundInEcosystem |
P22357
|
FINISHED |
| Object | montane 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: montane forest | Statement: [Lincoln Tree, foundInEcosystem, montane forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInEcosystem Context triple: [Lincoln Tree, foundInEcosystem, montane forest]
-
A.
partOfEcosystem
Indicates that an entity functions as a component within a larger ecological system, contributing to and affected by its interactions and processes.
-
B.
containsEcosystem
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
-
C.
hasAquaticEcosystem
Indicates that an entity possesses, contains, or is associated with an ecosystem primarily based in water (such as rivers, lakes, wetlands, or oceans).
-
D.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
E.
featuresHabitat
chosen
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b04c03481908d901788ce2c4128 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77bf1ef08190bb3487b3f3ee088c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.