Triple
T38497660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 宇治川 |
E919737
|
entity |
| Predicate | 流域の名産 |
P190964
|
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 the primary industries or economic activities that are characteristic of and predominantly carried out within a given river basin.
-
B.
架かる川
Indicates that a river spans or lies beneath something like a bridge or structure that is set over it.
-
C.
hasLocalNameForRiver
Indicates that an entity specifies the locally used name for a particular river.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
isRegionalRiver
Indicates that a river is classified as a regional river, typically limited in geographic extent and significance to a specific region rather than being a major or national waterway.
- F. None of above. chosen
Provenance (4 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_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd31227708190a7df213597e66ca8 |
completed | May 7, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.