Triple
T35290361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SV Kwakel |
E1019203
|
entity |
| Predicate | located in province |
P182217
|
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: [SV Kwakel, located in province, North Holland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: located in province Context triple: [SV Kwakel, located in province, North Holland]
-
A.
stationedInProvince
Indicates that an entity is assigned or based in a particular province as its location or area of operation.
-
B.
locatedInCountryCapitalOfProvince
Indicates that an entity is located in the country that contains the capital city of a specified province.
-
C.
positionWithinProvince
chosen
Indicates that one entity’s location lies inside the geographic or administrative boundaries of a specified province.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
foundedInProvince
Indicates that an entity (such as an organization or institution) was established or founded within a specific 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_69f76de7eedc8190a3bdc64ebbc05b42 |
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.