Triple
T16519780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 木曽川 |
E401286
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | 長良川 |
E738298
|
NE 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: [木曽川, hasTributary, 長良川]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 長良川 Context triple: [木曽川, hasTributary, 長良川]
-
A.
長良川
chosen
長良川 is a major river in central Japan renowned for its clear waters, traditional cormorant fishing, and scenic valleys flowing through Gifu Prefecture.
-
B.
鴨川
鴨川は京都市中心部を南北に流れ、四季折々の風景や川床などで知られる代表的な河川です。
-
C.
木曽川
木曽川 is a major river in central Japan that flows through the Kiso Valley and is known for its scenic beauty and historical importance as part of the Nōbi Plain river system.
-
D.
広瀬川
広瀬川 is a river in Miyagi Prefecture, Japan, known for flowing through Sendai and featuring prominently in local scenery and culture.
-
E.
Sagami River
The Sagami River is a major river in central Japan that flows through Yamanashi and Kanagawa Prefectures before reaching the Pacific Ocean.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7f8a1481909fe6b3c16a72059b |
completed | April 18, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006ed6627081909dae6b4259a5609c |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 10, 2026, 5:14 a.m.