Triple
T2681920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Reorganization Act |
E57391
|
entity |
| Predicate | policyShiftFrom |
P9880
|
FINISHED |
| Object | assimilation |
—
|
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: assimilation | Statement: [Indian Reorganization Act, policyShiftFrom, assimilation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyShiftFrom Context triple: [Indian Reorganization Act, policyShiftFrom, assimilation]
-
A.
policyShift
chosen
Indicates a change or adjustment in an existing policy, typically reflecting a new direction, priority, or approach.
-
B.
changePolicy
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
-
C.
policyTool
Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
-
D.
partySwitch
Indicates that an entity changes its affiliation from one political party to another.
-
E.
policyApproach
Indicates the strategy, method, or overall course of action adopted in creating, implementing, or managing a policy.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abda2f7bf88190a1e3103dd014d871 |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ab9d08190b72b6104c6dbc769 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.