Triple

T35800388
Position Surface form Disambiguated ID Type / Status
Subject 利根川 E1034958 entity
Predicate 水系名 P16952 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. watercourseName chosen
    Indicates the name assigned to a river, stream, or other flowing body of water in the relationship.
  • B. riverSystem
    Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
  • C. isWatercourseOf
    Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
  • D. 母河流
    Indicates that a river is the main or parent river from which another river (such as a tributary or distributary) originates or to which it belongs.
  • E. waterwaySystem
    Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
  • 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_69f76e169bd081909f16cd8c9ee7870c completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a258a1a88190ad421d43295d376c completed May 3, 2026, 7:30 p.m.
PD Predicate disambiguation batch_69f7a070e23881909a233370acb57384 completed May 3, 2026, 7:22 p.m.
Created at: May 3, 2026, 4:06 p.m.