Triple
T30963570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War Measures Act (Canada) |
E788890
|
entity |
| Predicate | invocationDate |
P170850
|
FINISHED |
| Object | 1914-08-22 |
—
|
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: 1914-08-22 | Statement: [War Measures Act (Canada), invocationDate, 1914-08-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invocationDate Context triple: [War Measures Act (Canada), invocationDate, 1914-08-22]
-
A.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
B.
referralDate
Indicates the date on which a referral from one party to another was made or formally recorded.
-
C.
inscriptionDate
Indicates the date on which an inscription was created, carved, or formally recorded.
-
D.
appliedDate
Indicates the date on which an application or request was submitted or made.
-
E.
allegedInvolvementDate
Indicates the date on which an entity is claimed or reported to have been involved in a particular event or activity, without asserting that the involvement is confirmed.
- F. None of above. chosen
Provenance (4 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:54 p.m.