Triple

T38133743
Position Surface form Disambiguated ID Type / Status
Subject Royal Oak station E952291 entity
Predicate hasStationEntranceOn P1974 FINISHED
Object Lord Hill’s Bridge
Lord Hill’s Bridge is a road bridge in the Paddington area of London that provides access over the railway lines near Royal Oak Underground station.
E2285789 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: Lord Hill’s Bridge | Statement: [Royal Oak station, hasStationEntranceOn, Lord Hill’s Bridge]
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: Lord Hill’s Bridge
Triple: [Royal Oak station, hasStationEntranceOn, Lord Hill’s Bridge]
Generated description
Lord Hill’s Bridge is a road bridge in the Paddington area of London that provides access over the railway lines near Royal Oak Underground station.

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_69f76f083548819082bd2bbf53c79e8e completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fc45ebd5a48190af99801e4ff329c5 completed May 7, 2026, 7:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a4617d5a6b48190919aa1a5cac08619 completed July 2, 2026, 7:48 a.m.
NEDg Description generation batch_6a4618fe7b9881909645cb58af469303 completed July 2, 2026, 7:53 a.m.
NED2 Entity disambiguation (via description) batch_6a461e8937b88190802203a0194bae0c completed July 2, 2026, 8:17 a.m.
Created at: May 3, 2026, 4:21 p.m.