Triple
T27678723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Surrey |
E697849
|
entity |
| Predicate | serviceOperatorHeadquarters |
P95731
|
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: [Queen of Surrey, serviceOperatorHeadquarters, Victoria, British Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceOperatorHeadquarters Context triple: [Queen of Surrey, serviceOperatorHeadquarters, Victoria, British Columbia]
-
A.
operatedByCompanyHeadquarteredIn
Indicates that an entity is operated by a company whose headquarters is located in a specified place.
-
B.
serviceBranchHeadquarters
Indicates the location that serves as the main headquarters for a particular military or service branch.
-
C.
hasOperatorHeadquartersIn
chosen
Indicates that the primary operational headquarters of an operator is located in a specified place.
-
D.
employerHeadquarters
Indicates the location where an employer’s main corporate offices or central administrative operations are based.
-
E.
hasHeadquartersRoleFor
Indicates that an entity holds a specific role or position within the headquarters of another entity.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 2:45 p.m.