Triple
T38497651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 宇治川 |
E919737
|
entity |
| Predicate | 下流名 |
P147346
|
FINISHED |
| Object | 淀川 |
—
|
NE NERFINISHED |
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 the name of the downstream area or region that lies in the lower part of a river, system, or flow relative to a reference point.
-
B.
hasLowerCourseName
Indicates that one course’s name is lexicographically or alphabetically lower (comes before) another course’s name.
-
C.
downstreamUse
Indicates that one entity makes use of the outputs, results, or products generated by another entity at a later stage in a process or workflow.
-
D.
hasNameInLowerCourse
chosen
Indicates that an entity (such as a river or watercourse) is known by a particular name specifically in its lower course or downstream section.
-
E.
lowerCourseName
Indicates that the course’s name is represented in all lowercase characters.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.