Triple
T20144811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tillamook Burn |
E491274
|
entity |
| Predicate | reforestationPeak |
P138837
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Tillamook Burn, reforestationPeak, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reforestationPeak Context triple: [Tillamook Burn, reforestationPeak, 1950s]
-
A.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
-
B.
summitAboveTreeline
Indicates that the summit of a landform is located above the natural treeline, where trees no longer grow due to environmental conditions.
-
C.
isEasternPeakOf
Indicates that one peak is the eastern member or counterpart within a set or pair of related peaks.
-
D.
centralPeak
Indicates that one entity is the central, elevated peak located near the middle of another entity, typically within a larger structure such as a crater or basin.
-
E.
depictsPeak
Indicates that one entity visually represents or portrays the highest or most intense point of another entity or process.
- F. None of above. chosen
Provenance (4 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679d89688190ae88d81002d16d6e |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:33 p.m.