Triple

T28813719
Position Surface form Disambiguated ID Type / Status
Subject 名神高速道路 E727581 entity
Predicate 関連計画 P98771 FINISHED
Object 国土開発幹線自動車道
国土開発幹線自動車道は、日本全国の主要都市や地域を結ぶことを目的とした基幹的な高速自動車道路網の総称である。
 E1833540 NE FINISHED

How this triple was built (3 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: [名神高速道路, 関連計画, 国土開発幹線自動車道]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 国土開発幹線自動車道
Triple: [名神高速道路, 関連計画, 国土開発幹線自動車道]
Generated description
国土開発幹線自動車道は、日本全国の主要都市や地域を結ぶことを目的とした基幹的な高速自動車道路網の総称である。
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: 関連計画
Context triple: [名神高速道路, 関連計画, 国土開発幹線自動車道]
  • A. hasRelatedPlan chosen
    Indicates that one entity is associated with another entity through a plan that is relevant or connected to it.
  • B. plannedUnder
    Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
  • C. plannedWith
    Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
  • D. hasPlanningAssociation
    Indicates a relationship where one entity is involved with, linked to, or considered in the planning or preparation activities of another entity.
  • E. planned
    Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
  • F. None of above.

Provenance (6 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_69f0319c38948190bca746ad60fd25ba completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f658f163a88190b1dd222eaa0f93ea completed May 2, 2026, 8:05 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24a28238988190815a8a5c3fc15fea completed June 6, 2026, 10:43 p.m.
NEDg Description generation batch_6a24a650b8408190abe70dc1108b8368 completed June 6, 2026, 10:59 p.m.
NED2 Entity disambiguation (via description) batch_6a24aa401b2c8190bf774922baa12667 completed June 6, 2026, 11:16 p.m.
PD Predicate disambiguation batch_69f65762b5e481908a30ca963dcba4be completed May 2, 2026, 7:58 p.m.
Created at: April 28, 2026, 6:32 a.m.