Triple
T2910578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Water Information System |
E63672
|
entity |
| Predicate | dataUpdateFrequency |
P16914
|
FINISHED |
| Object | real time for many streamgages |
—
|
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: real time for many streamgages | Statement: [National Water Information System, dataUpdateFrequency, real time for many streamgages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataUpdateFrequency Context triple: [National Water Information System, dataUpdateFrequency, real time for many streamgages]
-
A.
rotationPeriod_hours
Indicates the length of time, measured in hours, that an object takes to complete one full rotation on its axis.
-
B.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
C.
broadcastFrequency
Indicates the specific radio or transmission frequency at which a broadcast is sent or received.
-
D.
performedFrequency
chosen
Indicates how often an action or activity is carried out within a given time period.
-
E.
dataMaintained
Indicates that one entity is responsible for preserving, storing, or keeping another entity’s data up to date and accessible over time.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0e899808190a348e1e71116d0a5 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.