Triple

T25267247
Position Surface form Disambiguated ID Type / Status
Subject Geldersekade E633463 entity
Predicate connectedTo P37 FINISHED
Object Prins Hendrikkade
Prins Hendrikkade is a major waterfront street in central Amsterdam, running along the city’s historic harbor and serving as a key traffic and transport artery near Amsterdam Centraal Station.
E1678575 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: Prins Hendrikkade | Statement: [Geldersekade, connectedTo, Prins Hendrikkade]
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: Prins Hendrikkade
Triple: [Geldersekade, connectedTo, Prins Hendrikkade]
Generated description
Prins Hendrikkade is a major waterfront street in central Amsterdam, running along the city’s historic harbor and serving as a key traffic and transport artery near Amsterdam Centraal Station.

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_69e75a92f48881909974ff9c11150a2e completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f48b9b687881908fd87a2f5fa0b1e7 completed May 1, 2026, 11:16 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10896f9a8081908edb3db726d26589 completed May 22, 2026, 4:50 p.m.
NEDg Description generation batch_6a108a2504b8819085f07ef035e63915 completed May 22, 2026, 4:53 p.m.
NED2 Entity disambiguation (via description) batch_6a108b00aee0819088928d399c5e52b7 completed May 22, 2026, 4:57 p.m.
Created at: April 21, 2026, 1:16 p.m.