Triple
T18559209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corbones River |
E453585
|
entity |
| Predicate | hasBasinCharacteristic |
P29610
|
FINISHED |
| Object | largely rural |
—
|
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 rural | Statement: [Corbones River, hasBasinCharacteristic, largely rural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasinCharacteristic Context triple: [Corbones River, hasBasinCharacteristic, largely rural]
-
A.
hasWatershedCharacteristic
chosen
Indicates that a watershed possesses a specified characteristic, feature, or property.
-
B.
basinFeature
Indicates that one entity is a physical feature or component located within or forming part of a basin.
-
C.
hasRiverineCharacteristic
Indicates that something possesses qualities, features, or conditions associated with rivers or river environments.
-
D.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
E.
hasWaterBasins
Indicates that one entity possesses, contains, or includes one or more water basins in relation to 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53808c3fc8190aac38b29296cee13 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:42 a.m.