Triple
T30527195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Luis Obispo Creek |
E776882
|
entity |
| Predicate | hasRiparianVegetation |
P180644
|
FINISHED |
| Object | willows |
—
|
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: willows | Statement: [San Luis Obispo Creek, hasRiparianVegetation, willows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiparianVegetation Context triple: [San Luis Obispo Creek, hasRiparianVegetation, willows]
-
A.
hasRiparianZone
Indicates that an area is adjacent to and ecologically influenced by a body of water, forming its riparian (riverbank or shoreline) zone.
-
B.
containsWetland
Indicates that one area or region includes within its boundaries a wetland ecosystem.
-
C.
hasNearbyWetlandRegion
Indicates that a given location or area is situated close to, or in the vicinity of, a wetland region.
-
D.
isCoastalOrRiverine
Indicates that a place is located along a sea coast or adjacent to a river, reflecting a shoreline or riverbank relationship.
-
E.
hasFloodplains
Indicates that an area or region includes land that is subject to flooding, typically adjacent to a river or water body.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 29, 2026, 8:17 p.m.