Triple

T24447056
Position Surface form Disambiguated ID Type / Status
Subject Rotterdam urban bus network E616432 entity
Predicate hasServiceArea P82 FINISHED
Object Rotterdam North
Rotterdam North is a district of Rotterdam in the Netherlands, characterized by its residential neighborhoods, local commerce, and connectivity to the rest of the city via public transport.
E1646228 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: Rotterdam North | Statement: [Rotterdam urban bus network, hasServiceArea, Rotterdam North]
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: Rotterdam North
Triple: [Rotterdam urban bus network, hasServiceArea, Rotterdam North]
Generated description
Rotterdam North is a district of Rotterdam in the Netherlands, characterized by its residential neighborhoods, local commerce, and connectivity to the rest of the city via public transport.

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_69e2d7edca608190aafefc8877a1b4da completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f298546ea481908a7343a80ba096a6 completed April 29, 2026, 11:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a100fddb5a48190be86238727203acb completed May 22, 2026, 8:12 a.m.
NEDg Description generation batch_6a10136871588190b4e4b4618ab7a400 completed May 22, 2026, 8:27 a.m.
NED2 Entity disambiguation (via description) batch_6a10141161b08190b471a7882a4d8aa0 completed May 22, 2026, 8:30 a.m.
Created at: April 18, 2026, 2:17 a.m.