Triple
T36354300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neskowin Ghost Forest |
E895296
|
entity |
| Predicate | preservationProcess |
P21580
|
FINISHED |
| Object | waterlogging |
—
|
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: waterlogging | Statement: [Neskowin Ghost Forest, preservationProcess, waterlogging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservationProcess Context triple: [Neskowin Ghost Forest, preservationProcess, waterlogging]
-
A.
preservationMethod
chosen
Indicates the technique or process used to maintain, protect, or prolong the condition, quality, or usability of something over time.
-
B.
preservationFunction
Indicates that one entity serves to maintain, protect, or keep another entity in its original or intended state over time.
-
C.
preservationType
Indicates the method or process by which something is preserved or kept from deterioration.
-
D.
preservationFocus
Indicates that the primary concern or emphasis is on maintaining, protecting, or conserving something in its existing or intended state.
-
E.
preservationUse
Indicates that something is used, designed, or intended specifically for the purpose of preserving or maintaining another entity in its existing state.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:09 p.m.