Triple

T26724050
Position Surface form Disambiguated ID Type / Status
Subject Schwabentor E673785 entity
Predicate locatedOn P40 FINISHED
Object Oberlinden square
Oberlinden square is a historic plaza in Freiburg im Breisgau’s old town, known for its picturesque setting near the Schwabentor city gate and traditional architecture.
E1740593 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: Oberlinden square | Statement: [Schwabentor, locatedOn, Oberlinden square]
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: Oberlinden square
Triple: [Schwabentor, locatedOn, Oberlinden square]
Generated description
Oberlinden square is a historic plaza in Freiburg im Breisgau’s old town, known for its picturesque setting near the Schwabentor city gate and traditional architecture.

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_69eecda481d08190aea69f2f7c745f56 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f6180905dc819090453de138391b2c completed May 2, 2026, 3:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12093f66a4819084efa818822737bf completed May 23, 2026, 8:08 p.m.
NEDg Description generation batch_6a1209d4ee448190b8e3d8cdb44fc641 completed May 23, 2026, 8:11 p.m.
NED2 Entity disambiguation (via description) batch_6a120a4736688190939a60d04fe467e2 completed May 23, 2026, 8:12 p.m.
Created at: April 27, 2026, 3:41 a.m.