Triple
T33393506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HUC code |
E855111
|
entity |
| Predicate | 2-digitHUCAlsoCalled |
P112037
|
FINISHED |
| Object | region |
—
|
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: region | Statement: [HUC code, 2-digitHUCAlsoCalled, region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2-digitHUCAlsoCalled Context triple: [HUC code, 2-digitHUCAlsoCalled, region]
-
A.
hydrologicUnitCode
Indicates the standardized hydrologic unit identifier that specifies the drainage or watershed area associated with a given geographic feature or location.
-
B.
regionAlsoCalled
chosen
Indicates that a geographic or administrative region is known by an alternative name or alias.
-
C.
basinAbbreviation
Indicates that one entity is the standard abbreviated form of the name of a particular basin associated with the other entity.
-
D.
alsoServedByPostalCodeSystem
Indicates that the same geographic area or address is additionally covered or identified by another postal code system.
-
E.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:35 a.m.