Triple
T33459007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namekagon River |
E856855
|
entity |
| Predicate | hasWatercourseCharacteristic |
P58792
|
FINISHED |
| Object | free-flowing |
—
|
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: free-flowing | Statement: [Namekagon River, hasWatercourseCharacteristic, free-flowing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWatercourseCharacteristic Context triple: [Namekagon River, hasWatercourseCharacteristic, free-flowing]
-
A.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
B.
hasWaterBodyCharacteristic
chosen
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
C.
hasRiverineCharacteristic
Indicates that something possesses qualities, features, or conditions associated with rivers or river environments.
-
D.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
E.
hasWatershedCharacteristic
Indicates that a watershed possesses a specified characteristic, feature, or property.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:37 a.m.