Triple
T34258708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 九十九里浜 |
E878965
|
entity |
| Predicate | 関連道路 |
P131761
|
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.
roadAssociatedWith
chosen
Indicates that there is a relevant connection or linkage between a road and another entity, such as use, location, function, or impact.
-
B.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
C.
relatedRoadCar
Indicates that there is a contextual or functional association between a specific road and a specific car (e.g., the car uses, is located on, or is otherwise linked to that road).
-
D.
roadJunctionRelation
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
E.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.