Triple

T31188878
Position Surface form Disambiguated ID Type / Status
Subject Kálvin Square E795127 entity
Predicate hasPublicTransportConnection P3791 FINISHED
Object Budapest tram line 48
Budapest tram line 48 is a public tram route in Budapest, Hungary, serving central districts and connecting key inner-city locations.
E1952750 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: Budapest tram line 48 | Statement: [Kálvin Square, hasPublicTransportConnection, Budapest tram line 48]
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: Budapest tram line 48
Triple: [Kálvin Square, hasPublicTransportConnection, Budapest tram line 48]
Generated description
Budapest tram line 48 is a public tram route in Budapest, Hungary, serving central districts and connecting key inner-city locations.

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_69f224d7a6a481908187c4362a8a525f completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69913d91c81908d00dc873428367b completed May 3, 2026, 12:38 a.m.
NED1 Entity disambiguation (via context triple) batch_6a296bd3ee0c81909cb7043846b0bb13 completed June 10, 2026, 1:51 p.m.
NEDg Description generation batch_6a296eac8ee08190aca9d36aecb0163f completed June 10, 2026, 2:03 p.m.
NED2 Entity disambiguation (via description) batch_6a298d143e0081909a963f4bd5773165 completed June 10, 2026, 4:13 p.m.
Created at: April 29, 2026, 9:08 p.m.