Triple
T23644713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bois de la Cambre |
E583998
|
entity |
| Predicate | hasRoadRegulation |
P49787
|
FINISHED |
| Object | partial weekend car-free zones |
—
|
LITERAL 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: partial weekend car-free zones | Statement: [Bois de la Cambre, hasRoadRegulation, partial weekend car-free zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadRegulation Context triple: [Bois de la Cambre, hasRoadRegulation, partial weekend car-free zones]
-
A.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
-
B.
hasRoadSignConvention
Indicates that there is an established standard or system governing the design, meaning, or usage of road signs in a given context.
-
C.
hasTrafficRegime
chosen
Indicates that a specified traffic control or regulatory system applies to a given road, area, or transport context.
-
D.
hasRoadAuthority
Indicates that one entity holds official control, responsibility, or decision-making power over a road or road network in relation to another entity.
-
E.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2847ba08190ad2427a82fada698 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.