Triple
T534807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsushima Current |
E12302
|
entity |
| Predicate | flowsNortheastAlong |
P9306
|
FINISHED |
| Object | western coast of Japan |
—
|
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: western coast of Japan | Statement: [Tsushima Current, flowsNortheastAlong, western coast of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsNortheastAlong Context triple: [Tsushima Current, flowsNortheastAlong, western coast of Japan]
-
A.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
B.
flowsAlongCoastOf
chosen
Indicates that something, typically a body of water or current, moves in a path that follows and runs adjacent to a coastline.
-
C.
northernShore
Indicates that one entity is located on the northern shore or northern side of another entity, typically a body of water or coastline.
-
D.
locatedNorthEastOf
Indicates that one entity is positioned to the north-east of another entity in space.
-
E.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.