Triple
T28409821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sint-Stevens-Woluwe |
E719632
|
entity |
| Predicate | locatedInNUTS3 |
P103735
|
FINISHED |
| Object | BE241 Halle-Vilvoorde |
—
|
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: BE241 Halle-Vilvoorde | Statement: [Sint-Stevens-Woluwe, locatedInNUTS3, BE241 Halle-Vilvoorde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNUTS3 Context triple: [Sint-Stevens-Woluwe, locatedInNUTS3, BE241 Halle-Vilvoorde]
-
A.
locatedInNUTS2
Indicates that one entity is geographically situated within, or belongs to, a specific NUTS-2 (Nomenclature of Territorial Units for Statistics level 2) region.
-
B.
isLocatedInSubdivision
chosen
Indicates that one place or entity is situated within a more specific administrative or geographic subdivision of another area.
-
C.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
-
D.
locatedInRegionalCouncil
Indicates that one entity is geographically situated within the jurisdictional area governed by a specific regional council.
-
E.
locatedInHubOf
Indicates that one entity is situated within the central hub or core area associated with another entity.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: April 28, 2026, 1:25 a.m.