Triple
T19978364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braes Bayou Greenway |
E493749
|
entity |
| Predicate | waterwayTypeFollowed |
P17791
|
FINISHED |
| Object | bayou |
—
|
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: bayou | Statement: [Braes Bayou Greenway, waterwayTypeFollowed, bayou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayTypeFollowed Context triple: [Braes Bayou Greenway, waterwayTypeFollowed, bayou]
-
A.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
B.
waterwayClass
chosen
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
C.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
D.
followsWatercourse
Indicates that one entity runs alongside or traces the path of a watercourse such as a river, stream, or canal.
-
E.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d11108481908241a2a96a795a7d |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:27 p.m.