Triple
T27012364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuman River |
E680425
|
entity |
| Predicate | flowsIntoSea |
P8847
|
FINISHED |
| Object | Sea of Japan |
—
|
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: Sea of Japan | Statement: [Tuman River, flowsIntoSea, Sea of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsIntoSea Context triple: [Tuman River, flowsIntoSea, Sea of Japan]
-
A.
flowsIntoSeaArm
Indicates that a body of water (such as a river or stream) discharges its flow into a sea arm (a bay, fjord, or similar inlet of the sea).
-
B.
flowsIntoBodyOfWaterAt
Indicates that one body of water moves or drains into another body of water at a specific location or point.
-
C.
flowsAlongCoastOf
Indicates that something, typically a body of water or current, moves in a path that follows and runs adjacent to a coastline.
-
D.
flowsIntoBodyOfWaterType
chosen
Indicates that one body of water moves or drains into another body of water of a specified type (e.g., river, lake, ocean).
-
E.
flowsIntoBodyOfWaterNear
Indicates that one body of water flows into another body of water at or near a specific location.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621fd9e148190ad88ea06663957f8 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:04 a.m.