Triple
T11159293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Canada |
E263991
|
entity |
| Predicate | adoptedInPart |
P64654
|
FINISHED |
| Object | 1867 |
—
|
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: 1867 | Statement: [Constitution of Canada, adoptedInPart, 1867]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedInPart Context triple: [Constitution of Canada, adoptedInPart, 1867]
-
A.
adoptedAsPartOf
Indicates that one entity has been taken in, integrated, or accepted as a component or member within another entity or larger whole.
-
B.
partiallyIncorporatedInto
chosen
Indicates that one entity has been integrated or absorbed into another entity, but only to a limited or incomplete extent.
-
C.
adoptedInForm
Indicates that something is accepted, implemented, or brought into use within a particular form, format, or structural arrangement.
-
D.
adoptedPursuantTo
Indicates that something (such as a measure, policy, or decision) was formally adopted in accordance with, and on the basis of, a specific legal authority, procedure, or instrument.
-
E.
adopted
Indicates that one entity has legally taken another (often a child or animal) into its family or care as a permanent member.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e87fe9a881909540ecc4ed9b6b9f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.