Triple
T28813400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 富士川 |
E727575
|
entity |
| Predicate | 源流域 |
P38420
|
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.
上游所属流域
Indicates that a given upstream section of a river belongs to or is part of a particular drainage basin or watershed.
-
B.
sourceBasin
chosen
Indicates that one entity is the drainage basin or watershed from which another entity (such as a river segment or water body) originates or receives its source waters.
-
C.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
D.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
-
E.
hasHeadwatersOf
Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:31 a.m.