Triple
T11309819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 淀川 |
E267806
|
entity |
| Predicate | 国際流域コード |
P36928
|
FINISHED |
| Object | 太平洋側流域 |
—
|
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: 太平洋側流域 | Statement: [淀川, 国際流域コード, 太平洋側流域]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 国際流域コード Context triple: [淀川, 国際流域コード, 太平洋側流域]
-
A.
transboundaryBasin
Indicates that a river basin or watershed extends across and is shared by the territories of two or more political or administrative jurisdictions.
-
B.
hydrologicCodeSystem
chosen
Indicates the classification or coding system used to identify and organize hydrologic or water-related features.
-
C.
hydrologicUnitCode
Indicates the standardized hydrologic unit identifier that specifies the drainage or watershed area associated with a given geographic feature or location.
-
D.
transboundaryRiverOf
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
-
E.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c0b3b88190ac0e3d6a5ad3b9bc |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.