Triple

T31668628
Position Surface form Disambiguated ID Type / Status
Subject Keio Keibajō Line E808205 entity
Predicate nativeName P15 FINISHED
Object 京王競馬場線
京王競馬場線 is a short branch line of the Keio Corporation railway network in Tokyo that primarily serves Tokyo Racecourse.
E1971894 NE 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: [Keio Keibajō Line, nativeName, 京王競馬場線]
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: [Keio Keibajō Line, nativeName, 京王競馬場線]
Generated description
京王競馬場線 is a short branch line of the Keio Corporation railway network in Tokyo that primarily serves Tokyo Racecourse.

Provenance (5 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_69f348dbeef4819080b446a7feb6340b completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6aa2cefcc8190b872d631c6a7794e completed May 3, 2026, 1:51 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b79f094548190bdde22ff5a2cd619 completed June 12, 2026, 3:16 a.m.
NEDg Description generation batch_6a2b7af7ef5c8190982e97697b0647dc completed June 12, 2026, 3:20 a.m.
NED2 Entity disambiguation (via description) batch_6a2b7d5bc9ac8190a2fd81f84b509ec8 completed June 12, 2026, 3:30 a.m.
Created at: April 30, 2026, 11 p.m.