Triple
T35290210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amstelhoek |
E1019199
|
entity |
| Predicate | locatedNearProvincialBorderWith |
P61305
|
FINISHED |
| Object | North Holland |
E24160
|
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: North Holland | Statement: [Amstelhoek, locatedNearProvincialBorderWith, North Holland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearProvincialBorderWith Context triple: [Amstelhoek, locatedNearProvincialBorderWith, North Holland]
-
A.
locatedNearStateBorderWith
chosen
Indicates that one entity is situated geographically close to the border of a specified state.
-
B.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
-
C.
hasNearbySettlementAcrossBorder
Indicates that one settlement is located close to another settlement that lies just across an intervening political or administrative border.
-
D.
borderingCountryOfItsProvince
Indicates that one country shares a land border with the country to which a given province belongs.
-
E.
borderingCountryOfProvince
Indicates that a country shares a land or maritime border with the specified province.
- F. None of above.
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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38369ab8f881908d46272214d26df3 |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.