Triple
T35862725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional districts of British Columbia |
E1036996
|
entity |
| Predicate | serviceAreasInclude |
P82
|
FINISHED |
| Object | regional planning |
—
|
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: regional planning | Statement: [Regional districts of British Columbia, serviceAreasInclude, regional planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceAreasInclude Context triple: [Regional districts of British Columbia, serviceAreasInclude, regional planning]
-
A.
hasServiceAreas
Indicates that an entity provides services within, or is operational across, specific geographic or functional areas.
-
B.
areaOfService
Indicates the geographic or functional region within which a service is provided or applicable.
-
C.
serviceAreaName
Indicates the designated name of the geographic or functional area that a service covers or operates within.
-
D.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
E.
strategicAreaServed
Indicates that an entity provides services or exerts influence within a particular area considered strategically important.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:06 p.m.