Triple
T25911918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortensrud Church |
E652917
|
entity |
| Predicate | locatedInNaturalEnvironment |
P163099
|
FINISHED |
| Object | forest setting |
—
|
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 setting | Statement: [Mortensrud Church, locatedInNaturalEnvironment, forest setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNaturalEnvironment Context triple: [Mortensrud Church, locatedInNaturalEnvironment, forest setting]
-
A.
onlyNaturalHabitatOf
Indicates that a given location is the sole natural habitat where a particular species or organism occurs in the wild.
-
B.
isInNaturalSetting
chosen
Indicates that an entity exists or occurs within a natural, non-artificial environment or context.
-
C.
locatedInForest
Indicates that an entity is situated within the boundaries of a forest.
-
D.
naturalOccurrence
Indicates that the related event or phenomenon happens in nature without direct human intervention or artificial cause.
-
E.
locatedInParkLikeSetting
Indicates that something is situated within or directly surrounded by an environment resembling a park, typically featuring natural or landscaped outdoor elements.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 22, 2026, 8:30 a.m.