Triple
T13628024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schie River |
E325637
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Rotterdam |
E18419
|
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 | Statement: [Schie River, connects, Rotterdam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rotterdam Context triple: [Schie River, connects, Rotterdam]
-
A.
Rotterdam
chosen
Rotterdam is a major Dutch port city known for having one of the world’s largest harbors and striking modern architecture.
-
B.
Utrecht
Utrecht is a historic city and province in the central Netherlands, known for its medieval old town, canals, and role as a religious and cultural center.
-
C.
Utrecht
Utrecht is a small town in South Africa’s KwaZulu-Natal province, known for its scenic surroundings and historical significance dating back to the 19th century.
-
D.
Dordrecht
Dordrecht is a historic Dutch city in South Holland known as one of the oldest trading centers in the Netherlands, situated strategically within the Rhine–Meuse–Scheldt river delta.
-
E.
Osdorp
Osdorp is a residential neighborhood in the western part of Amsterdam, Netherlands, known for its post-war urban planning and multicultural population.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbe9d803481908101def32817b0eb |
completed | April 12, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d41d1108190be5193b246845f07 |
completed | May 3, 2026, 7:08 p.m. |
Created at: April 9, 2026, 9:51 p.m.