Triple
T16038861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumoine River |
E389039
|
entity |
| Predicate | watershedCharacteristic |
P29610
|
FINISHED |
| Object | largely undeveloped |
—
|
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: largely undeveloped | Statement: [Dumoine River, watershedCharacteristic, largely undeveloped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watershedCharacteristic Context triple: [Dumoine River, watershedCharacteristic, largely undeveloped]
-
A.
hydrologicalCharacteristic
Indicates a relationship where a hydrological feature or condition (such as water flow, level, or behavior) characterizes or describes another entity.
-
B.
hasWatershedCharacteristic
chosen
Indicates that a watershed possesses a specified characteristic, feature, or property.
-
C.
hydrologyFeature
Indicates a relationship where one entity is a hydrological feature (such as a body or flow of water) associated with or characterizing another entity.
-
D.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
E.
watershedType
Indicates the classification or category of a watershed associated with an entity (e.g., by hydrologic, ecological, or management type).
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.