Triple

T33174580
Position Surface form Disambiguated ID Type / Status
Subject Beppu Station E849131 entity
Predicate adjacentTo P224 FINISHED
Object Beppu Station bus terminal
Beppu Station bus terminal is a major local and intercity bus hub in Beppu, Ōita Prefecture, serving passengers traveling to hot spring resorts and surrounding areas.
E849131 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: Beppu Station bus terminal | Statement: [Beppu Station, adjacentTo, Beppu Station bus terminal]
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: Beppu Station bus terminal
Triple: [Beppu Station, adjacentTo, Beppu Station bus terminal]
Generated description
Beppu Station bus terminal is a major local and intercity bus hub in Beppu, Ōita Prefecture, serving passengers traveling to hot spring resorts and surrounding areas.

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_69f3495d06508190b0b7729982982cea completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d95844bc8190b38cc5b9b8ca4ed4 completed May 3, 2026, 5:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3525c873f481909b92e35fa56fed88 completed June 19, 2026, 11:19 a.m.
NEDg Description generation batch_6a352658df508190b57cce861ed4fb5c completed June 19, 2026, 11:22 a.m.
NED2 Entity disambiguation (via description) batch_6a35274ad9d88190a03c345e1f0e70e8 completed June 19, 2026, 11:26 a.m.
Created at: May 1, 2026, 1:29 a.m.