Triple

T34800800
Position Surface form Disambiguated ID Type / Status
Subject London–Cardiff E1003212 entity
Predicate isPartOf P10 FINISHED
Object Trans‑UK intercity network
The Trans‑UK intercity network is a long‑distance passenger rail system linking major British cities and regions, including routes such as London to Cardiff.
E125826 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: Trans‑UK intercity network | Statement: [London–Cardiff, isPartOf, Trans‑UK intercity network]
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: Trans‑UK intercity network
Triple: [London–Cardiff, isPartOf, Trans‑UK intercity network]
Generated description
The Trans‑UK intercity network is a long‑distance passenger rail system linking major British cities and regions, including routes such as London to Cardiff.

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_69f76db543808190b188c6c86a91491b completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77a89c4e88190a048e95d42b4a084 completed May 3, 2026, 4:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a376fabe43c8190803d59ef868042d0 completed June 21, 2026, 4:59 a.m.
NEDg Description generation batch_6a3772a547008190aad97e280ea89d79 completed June 21, 2026, 5:12 a.m.
NED2 Entity disambiguation (via description) batch_6a3772f88660819083885d586ce06753 completed June 21, 2026, 5:13 a.m.
Created at: May 3, 2026, 3:59 p.m.