Triple
T33884257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VV Gilze |
E868581
|
entity |
| Predicate | isBasedInProvince |
P75412
|
FINISHED |
| Object | North Brabant |
—
|
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: North Brabant | Statement: [VV Gilze, isBasedInProvince, North Brabant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBasedInProvince Context triple: [VV Gilze, isBasedInProvince, North Brabant]
-
A.
isInProvince
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
-
B.
stationedInProvince
chosen
Indicates that an entity is assigned or based in a particular province as its location or area of operation.
-
C.
isProvinceOf
Indicates that one region holds the administrative status of a province within, and is governed as a subnational division of, another political entity.
-
D.
foundedInProvince
Indicates that an entity (such as an organization or institution) was established or founded within a specific province.
-
E.
hasProvinceOrRegion
Indicates that one entity includes, is associated with, or is located within a specific province or region as an administrative or geographic subdivision.
- F. None of above.
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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.