Triple

T25341480
Position Surface form Disambiguated ID Type / Status
Subject North Brighton railway station E635424 entity
Predicate servesSuburb P82 FINISHED
Object Brighton
Brighton is a coastal suburb of Melbourne, Australia, known for its affluent residential character and iconic colorful bathing boxes along Brighton Beach.
E1674258 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 | Statement: [North Brighton railway station, servesSuburb, Brighton]
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
Triple: [North Brighton railway station, servesSuburb, Brighton]
Generated description
Brighton is a coastal suburb of Melbourne, Australia, known for its affluent residential character and iconic colorful bathing boxes along Brighton Beach.

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_69e75a99bd6481909476115b35b9a8e4 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f498b818008190a4240a7a2cbeedfd completed May 1, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1075b067788190b2eba868cb7a8201 completed May 22, 2026, 3:26 p.m.
NEDg Description generation batch_6a10765abfb881908ab8908e1e497f64 completed May 22, 2026, 3:29 p.m.
NED2 Entity disambiguation (via description) batch_6a107735ae30819095bf24d523279c69 completed May 22, 2026, 3:33 p.m.
Created at: April 21, 2026, 1:32 p.m.