Triple
T15530546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argichi River |
E370201
|
entity |
| Predicate | isInlandWater |
P110175
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Argichi River, isInlandWater, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInlandWater Context triple: [Argichi River, isInlandWater, true]
-
A.
isInlandWaterBody
chosen
Indicates that one entity is a body of water located inland (such as a lake, river, or reservoir) rather than part of the open ocean or sea.
-
B.
isInlandWaterBodyOf
Indicates that one water body is an inland (non-oceanic) water feature that is geographically part of, contained within, or associated with another entity.
-
C.
isInCountryWater
Indicates that one entity (typically a body of water or water area) is located within or belongs to the territorial waters of a specified country.
-
D.
isFreshwaterBody
Indicates that the referenced body of water consists primarily of non-saline (fresh) water rather than saltwater.
-
E.
isWaterway
Indicates that one entity is a water-based route or channel (such as a river, canal, or sea lane) used for travel or transport.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414773548190b3311515f9d957dd |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:05 a.m.