Triple
T29147492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRD |
E738810
|
entity |
| Predicate | hasSeatOfGovernmentIn |
P28539
|
FINISHED |
| Object | Victoria, British Columbia |
—
|
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: Victoria, British Columbia | Statement: [CRD, hasSeatOfGovernmentIn, Victoria, British Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeatOfGovernmentIn Context triple: [CRD, hasSeatOfGovernmentIn, Victoria, British Columbia]
-
A.
hasSeatOfAdministration
Indicates that an administrative body or jurisdiction has a specific place or location that serves as its central seat of governance or administration.
-
B.
hostsSeatOfGovernment
chosen
Indicates that a place serves as the location where a government’s central administrative or executive authority is based.
-
C.
seatOfGovernment
Indicates that a location serves as the administrative center where a government exercises its official authority and conducts its primary governing functions.
-
D.
countryOfSeat
Indicates the country in which an organization’s official seat, headquarters, or principal office is located.
-
E.
residenceOfHeadOfGovernment
Indicates the place where the head of government officially resides.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 28, 2026, 11:40 a.m.