Triple
T369894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution Act, 1867 |
E8244
|
entity |
| Predicate | cameIntoForceDate |
P1124
|
FINISHED |
| Object | 1867-07-01 |
—
|
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-07-01 | Statement: [Constitution Act, 1867, cameIntoForceDate, 1867-07-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoForceDate Context triple: [Constitution Act, 1867, cameIntoForceDate, 1867-07-01]
-
A.
cameIntoForceInYear
Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
-
B.
dateOfEnactment
chosen
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
C.
dateEnacted
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
-
D.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
E.
cameIntoForceRelatedDocument
Indicates that a document became legally effective or operational as a result of, or in connection with, another related document.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebfdb0608190b1794a871d0d237a |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.