Triple
T20855982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Militia Act of 1904 |
E513479
|
entity |
| Predicate | replacedOrUpdated |
P29646
|
FINISHED |
| Object | earlier Canadian militia legislation |
—
|
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: earlier Canadian militia legislation | Statement: [Militia Act of 1904, replacedOrUpdated, earlier Canadian militia legislation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedOrUpdated Context triple: [Militia Act of 1904, replacedOrUpdated, earlier Canadian militia legislation]
-
A.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
B.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
C.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
D.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
E.
createdToReplace
Indicates that one entity was intentionally created for the purpose of taking over the role, function, or position 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a81ac4819084a07625b8ed4ec5 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.