Triple
T2910551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Water Information System |
E63672
|
entity |
| Predicate | dataCoverage |
P42861
|
FINISHED |
| Object | nationwide |
—
|
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: nationwide | Statement: [National Water Information System, dataCoverage, nationwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCoverage Context triple: [National Water Information System, dataCoverage, nationwide]
-
A.
networkCoverage
Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
-
B.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
C.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
-
D.
providesCoverage
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
-
E.
altitudeCoverageCharacteristic
Indicates the range or specific values of altitude over which something (such as a system, sensor, or service) is designed to operate or provide coverage.
- 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_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. |
| PDg | Predicate description generation | batch_69abddedd72c819094a9c4161af07780 |
completed | March 7, 2026, 8:12 a.m. |
Created at: March 6, 2026, 10:11 p.m.