Triple
T19485194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Route 308 |
E487493
|
entity |
| Predicate | hasRoadSection |
P85887
|
FINISHED |
| Object | steep narrow section between Osaka and Nara |
—
|
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: steep narrow section between Osaka and Nara | Statement: [National Route 308, hasRoadSection, steep narrow section between Osaka and Nara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadSection Context triple: [National Route 308, hasRoadSection, steep narrow section between Osaka and Nara]
-
A.
hasRoadComponent
chosen
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
B.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
C.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
D.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
-
E.
hasRoadConfiguration
Indicates that there exists a specific arrangement or layout of roads associated with or characterizing an 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6343f46e88190b7ba65c210285bee |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.