Triple

T28268289
Position Surface form Disambiguated ID Type / Status
Subject U-Bahn line U1 E712768 entity
Predicate connectsInnerCityAreas P177095 FINISHED
Object central Berlin LITERAL 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: central Berlin | Statement: [U-Bahn line U1, connectsInnerCityAreas, central Berlin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsInnerCityAreas
Context triple: [U-Bahn line U1, connectsInnerCityAreas, central Berlin]
  • A. connectsCentralDistrictsWith chosen
    Indicates a relationship where something serves as a link or route joining central districts to one another.
  • B. connectsCity
    Indicates a relationship where one entity serves as a link or route that joins or provides direct access between two cities.
  • C. connectsCityTo
    Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
  • D. connectsArea
    Indicates that one area serves as a link or passage between two other areas, enabling movement or interaction between them.
  • E. connectsMetroAreas
    Indicates a relationship where a transportation route or service links two or more metropolitan areas, enabling direct travel or interaction between them.
  • F. None of above.

Provenance (3 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_69efb5216c6881908020dce4aea65381 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69fd474b7e788190a9bb9b542d878f60 completed May 8, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69fd46d8b2f0819099d92d72c902f60e completed May 8, 2026, 2:13 a.m.
Created at: April 27, 2026, 11:16 p.m.