Triple
T12821170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Seal of the Province of British Columbia |
E306531
|
entity |
| Predicate | hasDesignApprovedBy |
P40769
|
FINISHED |
| Object | monarch of Canada |
—
|
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: monarch of Canada | Statement: [Great Seal of the Province of British Columbia, hasDesignApprovedBy, monarch of Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignApprovedBy Context triple: [Great Seal of the Province of British Columbia, hasDesignApprovedBy, monarch of Canada]
-
A.
hasDesigned
Indicates that one entity is the creator or designer of another entity.
-
B.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
C.
hasDesignAuthority
chosen
Indicates that one entity holds the recognized power or responsibility to make or approve design decisions affecting another entity.
-
D.
designApprovedInYear
Indicates that a particular design received formal approval in the specified year.
-
E.
designStatus
Indicates the current state or phase of progress for a design within its lifecycle.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9e5a2481908921d097df541db8 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d964100f7481909a197396003d4a71 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.