Triple

T28009403
Position Surface form Disambiguated ID Type / Status
Subject RAF Hartford Bridge E707371 entity
Predicate locatedNear P294 FINISHED
Object Hartford Bridge
Hartford Bridge is a village in Hampshire, England, situated near the former Royal Air Force station RAF Hartford Bridge (now known as Blackbushe Airport).
E1967423 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: Hartford Bridge | Statement: [RAF Hartford Bridge, locatedNear, Hartford 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: Hartford Bridge
Triple: [RAF Hartford Bridge, locatedNear, Hartford Bridge]
Generated description
Hartford Bridge is a village in Hampshire, England, situated near the former Royal Air Force station RAF Hartford Bridge (now known as Blackbushe Airport).

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_69ef96ba350c81908230d0b501b974c4 completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f63bd9241c8190af8074df6ead4b4b completed May 2, 2026, 6 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2b2d566d808190be1a912f41a10309 completed June 11, 2026, 9:49 p.m.
NEDg Description generation batch_6a2b302cf4e081909f90d2dd5051e185 completed June 11, 2026, 10:01 p.m.
NED2 Entity disambiguation (via description) batch_6a2b30f43dd48190bc9a9ffd91ce595d completed June 11, 2026, 10:04 p.m.
Created at: April 27, 2026, 8:02 p.m.