Triple
T23865505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarnaism |
E592565
|
entity |
| Predicate | viewOnForest |
P48151
|
FINISHED |
| Object | forests and groves protected as sacred spaces |
—
|
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: forests and groves protected as sacred spaces | Statement: [Sarnaism, viewOnForest, forests and groves protected as sacred spaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnForest Context triple: [Sarnaism, viewOnForest, forests and groves protected as sacred spaces]
-
A.
viewOnSanctuary
Indicates that an entity holds a particular perspective, opinion, or stance regarding a sanctuary or sanctuary-related concept.
-
B.
viewOnNature
chosen
Indicates a person's general attitude, perspective, or philosophy regarding nature and the natural environment.
-
C.
locatedInForest
Indicates that an entity is situated within the boundaries of a forest.
-
D.
isForested
Indicates that an area or region is covered predominantly by forest or dense tree vegetation.
-
E.
forestDistrict
Indicates that one entity functions as the forest district or forest management administrative unit responsible for the other entity.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae318cc8190afd0915517964494 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.