Triple
T6889917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NDSM Wharf |
E159018
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | IJ river |
E243500
|
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: IJ river | Statement: [NDSM Wharf, locatedOn, IJ river]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IJ river Context triple: [NDSM Wharf, locatedOn, IJ river]
-
A.
IJ river
chosen
The IJ river is a body of water in Amsterdam that functions as a key waterfront and harbor area for the city.
-
B.
Jiri River
The Jiri River is a tributary watercourse that feeds into the Barak River in northeastern India, contributing to the region’s fluvial network and drainage system.
-
C.
Gianh River
The Gianh River is a historically significant river in central Vietnam, known as a former boundary between northern and southern regions of the country.
-
D.
Jasien River
The Jasien River is a small watercourse in central Poland that flows through the city of Łódź and historically supported its early industrial development.
-
E.
Sym River
The Sym River is a significant waterway in central Siberia that flows through the Krasnoyarsk Krai region of Russia.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d9117c84819093dad7b765337b63 |
completed | March 27, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c748d16e5c81909e35db99af5cfa51 |
completed | March 28, 2026, 3:19 a.m. |
Created at: March 27, 2026, 2:23 p.m.