Triple
T11215771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drogenbos |
E265435
|
entity |
| Predicate | hasFacilityStatusFor |
P97885
|
FINISHED |
| Object | French-speaking residents |
—
|
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: French-speaking residents | Statement: [Drogenbos, hasFacilityStatusFor, French-speaking residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacilityStatusFor Context triple: [Drogenbos, hasFacilityStatusFor, French-speaking residents]
-
A.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
B.
appliesToFacility
Indicates that something (such as a rule, policy, condition, or attribute) is relevant to, valid for, or in effect at a particular facility.
-
C.
isWithinFacility
Indicates that one entity is physically located inside the boundaries or premises of a specified facility.
-
D.
isPrimaryFacilityFor
Indicates that one facility serves as the main or principal location responsible for supporting or serving a particular entity or operation.
-
E.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
- F. None of above. chosen
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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8e8eef48190932a85784ce15c86 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.