Triple
T2085632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redwood Creek |
E45342
|
entity |
| Predicate | vegetationTypeAlongBanks |
P953
|
FINISHED |
| Object | coast redwood (Sequoia sempervirens) |
—
|
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: coast redwood (Sequoia sempervirens) | Statement: [Redwood Creek, vegetationTypeAlongBanks, coast redwood (Sequoia sempervirens)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vegetationTypeAlongBanks Context triple: [Redwood Creek, vegetationTypeAlongBanks, coast redwood (Sequoia sempervirens)]
-
A.
vegetationType
chosen
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
B.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
C.
landscapeType
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
-
D.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
E.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba54ec048190bfe378aef1cc8086 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.