Triple

T29519266
Position Surface form Disambiguated ID Type / Status
Subject Brighton, East Sussex, England E748885 entity
Predicate hasFeature P182 FINISHED
Object Brighton Beach
Brighton Beach is a famous pebble beach and seaside resort area on England’s south coast, known for its vibrant promenade, historic pier, and lively cultural scene.
E1875108 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: Brighton Beach | Statement: [Brighton, East Sussex, England, hasFeature, Brighton Beach]
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: Brighton Beach
Triple: [Brighton, East Sussex, England, hasFeature, Brighton Beach]
Generated description
Brighton Beach is a famous pebble beach and seaside resort area on England’s south coast, known for its vibrant promenade, historic pier, and lively cultural scene.

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_69f0bd461c208190bec20bbf24e02cc5 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66c97ee788190a4ef192d3141fa57 completed May 2, 2026, 9:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a262d57bfd0819098a4b9d1201d5d38 completed June 8, 2026, 2:47 a.m.
NEDg Description generation batch_6a2638b11aa4819084fe5d23124d2dea completed June 8, 2026, 3:36 a.m.
NED2 Entity disambiguation (via description) batch_6a26390545d881908bf7eeffc5b18fb0 completed June 8, 2026, 3:37 a.m.
Created at: April 28, 2026, 4:39 p.m.