Triple
T20764654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazos River Authority |
E511062
|
entity |
| Predicate | useTypeServed |
P48322
|
FINISHED |
| Object | municipal water use |
—
|
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: municipal water use | Statement: [Brazos River Authority, useTypeServed, municipal water use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useTypeServed Context triple: [Brazos River Authority, useTypeServed, municipal water use]
-
A.
isServedFor
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
-
B.
servesDestinationType
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
-
C.
usesServerType
Indicates that an entity operates on, is hosted by, or otherwise relies on a specific type or category of server.
-
D.
servesType
chosen
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
E.
servesUse
Indicates that one entity is used by or functions to serve the purpose or needs of another 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24b18b8819082e61104be6f83a3 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:36 p.m.