Triple
T31027092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockel Square |
E790608
|
entity |
| Predicate | servesLocalPopulationOf |
P79065
|
FINISHED |
| Object | Woluwe-Saint-Pierre |
—
|
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: Woluwe-Saint-Pierre | Statement: [Stockel Square, servesLocalPopulationOf, Woluwe-Saint-Pierre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesLocalPopulationOf Context triple: [Stockel Square, servesLocalPopulationOf, Woluwe-Saint-Pierre]
-
A.
inhabitantsServed
Indicates the relationship in which a service, facility, or resource provides for or meets the needs of a specified group of inhabitants.
-
B.
servesNearbyCommunities
Indicates that an entity provides services or support to communities located in its surrounding area.
-
C.
servesPopulationCentre
chosen
Indicates that one entity provides services or functions in support of a particular population centre.
-
D.
servesCitizensOf
Indicates that an entity provides services, support, or functions on behalf of the citizens of a specified place or jurisdiction.
-
E.
servesTownship
Indicates that an entity provides official services or administrative functions to a particular township.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: April 29, 2026, 8:58 p.m.