Triple
T23201570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hekelingen–Piershil ferry |
E580325
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Piershil |
—
|
NE NERFINISHED |
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: Piershil | Statement: [Hekelingen–Piershil ferry, connects, Piershil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piershil Context triple: [Hekelingen–Piershil ferry, connects, Piershil]
-
A.
Piershil
chosen
Piershil is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
-
B.
Piersna
Piersna is a small village located within the administrative district of Gmina Pęcław in western Poland.
-
C.
Torysky
Torysky is a small village and municipality located in the Levoča District of the Prešov Region in eastern Slovakia.
-
D.
Parnis
Parnis is an alternative name for Parnes, which may refer to various places or entities sharing that designation.
-
E.
Polyanka
Polyanka is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line, located near the city center and serving the surrounding Polyanka Street area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f19079c44881909e8677921b08b931 |
completed | April 29, 2026, 5 a.m. |
Created at: April 17, 2026, 4:06 p.m.