Triple
T4284344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Tomas Aquino Creek |
E97228
|
entity |
| Predicate | hasFloodControlChannelSections |
P34520
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [San Tomas Aquino Creek, hasFloodControlChannelSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloodControlChannelSections Context triple: [San Tomas Aquino Creek, hasFloodControlChannelSections, yes]
-
A.
hasFloodControlStructure
Indicates that an entity possesses or is equipped with a structure designed to manage, control, or mitigate flooding.
-
B.
providesFloodControlFor
Indicates that one entity offers protection or mitigation against flooding for another entity or area.
-
C.
hasChannelizedSection
chosen
Indicates that a segment of a feature (such as a watercourse or flow path) has been modified or confined into an artificial or engineered channel.
-
D.
hasCanalSection
Indicates a relationship where one entity includes, contains, or is associated with a specific section or segment of a canal.
-
E.
hasFloodProtectionProject
Indicates that a flood protection project exists or is implemented for the referenced entity.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3503c062c81908f9a9eeab5381ec9 |
completed | March 12, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.