Triple
T13370848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Keewatin |
E319053
|
entity |
| Predicate | statusChanged |
P35872
|
FINISHED |
| Object | reintegrated into North-West Territories |
—
|
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: reintegrated into North-West Territories | Statement: [District of Keewatin, statusChanged, reintegrated into North-West Territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusChanged Context triple: [District of Keewatin, statusChanged, reintegrated into North-West Territories]
-
A.
statusChange
chosen
Indicates a transition in an entity’s state or condition from one status to another over time.
-
B.
statusChangeRule
Indicates a rule or condition that governs how and when an entity’s status is allowed to change from one state to another.
-
C.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
D.
statusInterface
Indicates that an entity serves as, or is associated with, an interface that reports or reflects its current status.
-
E.
status
Indicates the current condition, state, or standing of an entity within a given context.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd8950481909785a2060f43b6ed |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.