Triple
T162483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quebec Act |
E3316
|
entity |
| Predicate | altered |
P9
|
FINISHED |
| Object | system of colonial governance in Quebec |
—
|
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: system of colonial governance in Quebec | Statement: [Quebec Act, altered, system of colonial governance in Quebec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altered Context triple: [Quebec Act, altered, system of colonial governance in Quebec]
-
A.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
B.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
C.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
-
D.
influenced
chosen
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
-
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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2585a1a6481908899ad51211950e8 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256623704819089d9eeefe05858ce |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.