Triple
T29044255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buiksloterwegveer ferry |
E738087
|
entity |
| Predicate | nearbyLandmarkAtNorthBank |
P189720
|
FINISHED |
| Object | EYE Filmmuseum |
—
|
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: EYE Filmmuseum | Statement: [Buiksloterwegveer ferry, nearbyLandmarkAtNorthBank, EYE Filmmuseum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyLandmarkAtNorthBank Context triple: [Buiksloterwegveer ferry, nearbyLandmarkAtNorthBank, EYE Filmmuseum]
-
A.
municipalityOnNorthBank
Indicates that a municipality is located on the northern bank of a river or similar water body.
-
B.
stateOnNorthBank
Indicates that an entity is located on the northern bank of a river or similar water boundary.
-
C.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
D.
southernNearbyLandmark
Indicates that one landmark is located to the south and in close proximity to another landmark.
-
E.
northernTerminusNearbyPlace
Indicates that a place serves as, or is located very close to, the northern endpoint of a route, line, or similar feature.
- F. None of above. chosen
Provenance (4 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: April 28, 2026, 10:03 a.m.