Triple
T23745816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 豊後大野市 |
E586809
|
entity |
| Predicate | hasTransportation |
P105
|
FINISHED |
| Object |
JR九州豊肥本線
JR九州豊肥本線は、大分県と熊本県を結び、阿蘇山周辺などを走行する九州旅客鉄道(JR九州)の地方鉄道路線です。
|
E1599628
|
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: JR九州豊肥本線 | Statement: [豊後大野市, hasTransportation, JR九州豊肥本線]
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: JR九州豊肥本線 Triple: [豊後大野市, hasTransportation, JR九州豊肥本線]
Generated description
JR九州豊肥本線は、大分県と熊本県を結び、阿蘇山周辺などを走行する九州旅客鉄道(JR九州)の地方鉄道路線です。
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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcbded748190b305fc39ed71fa3f |
completed | April 29, 2026, 8:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0f53cf768c8190bd411c008451acd9 |
completed | May 21, 2026, 6:49 p.m. |
| NEDg | Description generation | batch_6a0f55d78200819088a55cdf614f4d76 |
completed | May 21, 2026, 6:58 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0f569011808190ba60d79b533d8e56 |
completed | May 21, 2026, 7:01 p.m. |
Created at: April 17, 2026, 7:12 p.m.