Triple
T731268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria, British Columbia |
E14834
|
entity |
| Predicate | isRegionalCentreFor |
P164
|
FINISHED |
| Object | southern Vancouver Island |
—
|
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: southern Vancouver Island | Statement: [Victoria, British Columbia, isRegionalCentreFor, southern Vancouver Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalCentreFor Context triple: [Victoria, British Columbia, isRegionalCentreFor, southern Vancouver Island]
-
A.
isMajorCenterOf
chosen
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
B.
hasResearchCentersIn
Indicates that an entity maintains or operates research centers located within a specified place or region.
-
C.
isNationalAdministrativeCenter
Indicates that a location serves as the primary administrative or governmental center for a nation.
-
D.
isServiceCentreFor
Indicates that one entity functions as a service center that provides support, maintenance, or related services for another entity.
-
E.
UNESCORegion
Indicates that an entity is associated with, classified under, or belongs to a specific UNESCO-designated geographic region.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f9b7608190bf97c8418a26e632 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.