Triple
T29511098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Route 9 |
E748653
|
entity |
| Predicate | traversesCoast |
P18703
|
FINISHED |
| Object | Sea of Japan coast |
—
|
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: Sea of Japan coast | Statement: [National Route 9, traversesCoast, Sea of Japan coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traversesCoast Context triple: [National Route 9, traversesCoast, Sea of Japan coast]
-
A.
COASTERRoute
Indicates a route or path specifically designated for a coaster (such as a roller coaster or similar ride) to travel along.
-
B.
extendsAlongCoastOf
chosen
Indicates that one entity stretches or runs parallel along the coastline of another entity.
-
C.
isCoastalTrail
Indicates that a trail is located along or near a coastline, typically following or closely paralleling the shore.
-
D.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
-
E.
followsCoast
Indicates that one entity’s path or boundary runs alongside and generally conforms to the shape of a coastline.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 4:32 p.m.